Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Idea: put all-cabal-files in ~/.stackage/update/ instead of ~/.stackage-update/ #6

Closed
DanBurton opened this issue Apr 29, 2015 · 3 comments

Comments

@DanBurton
Copy link

It seems nice for the user if stackage plugins all put their stuff in the same tree.

Sometime soon, Stackage.CLI will provide the getStackageRootIO :: IO FilePath function (currently defined in stackage-setup only), and it might be advisable to use that.

@snoyberg
Copy link
Member

I'm not sure I see this as a win, it seems decidedly in the "I wouldn't care personally" category. Maybe others have a thought on this?

@rvion
Copy link

rvion commented May 5, 2015

+1 for same root folder

I think that having all stackage related plugins share the same dedicated folder is more extensible, more rememberable, and could prevent later problems.

Random hypothetical bonus of having one common folder:

  • sharing the folder with some docker container
  • clean uninstall with rm -rf $STACKAGE_ROOT or rm -rf ~/.stackage (note that symlinks would not allow that behaviour)
  • versioning the whole folder to know what changed (git subfolder would automatically be handled nicely by git)
  • allowing the folder to be placed in an usual place for non regular systems with read only folders / disk
  • allowing the folder to be placed in an ssd disk instead of an regular drive

@snoyberg
Copy link
Member

snoyberg commented May 6, 2015

Change made

@snoyberg snoyberg closed this as completed May 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants