-
Notifications
You must be signed in to change notification settings - Fork 698
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
Investigate if the sandbox should ignore the user package DB #1183
Milestone
Comments
ghost
assigned 23Skidoo
Jan 15, 2013
This sounds like a bug. Can you explain in more detail what you did? |
|
Thanks, will look into it. |
We're probably using |
This was caused by 7b2e363. Setting |
23Skidoo
added a commit
to 23Skidoo/cabal
that referenced
this issue
Mar 24, 2013
In sandbox mode userInstallDirs = globalInstallDirs and we set userInstall to False to prevent UserPackageDB from being added to the package DB stack (see haskell#1183).
23Skidoo
added a commit
to 23Skidoo/cabal
that referenced
this issue
Mar 24, 2013
We use userInstallDirs in sandbox mode to prevent cabal-install from doing unnecessary things like invoking itself via 'sudo' (see commit 7b2e363 and 'rootCmd' in D.C.Install), but in this particular case we want userInstall to be False to prevent UserPackageDB from being added to the package DB stack (see haskell#1183 and interpretPackageDbFlags in D.S.Configure).
23Skidoo
added a commit
to 23Skidoo/cabal
that referenced
this issue
Mar 24, 2013
We use userInstallDirs in sandbox mode to prevent cabal-install from doing unnecessary things like invoking itself via 'sudo' (see commit 7b2e363 and 'rootCmd' in D.C.Install), but in this particular case we want userInstall to be False to prevent UserPackageDB from being added to the package DB stack (see haskell#1183 and interpretPackageDbFlags in D.S.Configure).
23Skidoo
added a commit
that referenced
this issue
Apr 12, 2013
We use userInstallDirs in sandbox mode to prevent cabal-install from doing unnecessary things like invoking itself via 'sudo' (see commit 7b2e363 and 'rootCmd' in D.C.Install), but in this particular case we want userInstall to be False to prevent UserPackageDB from being added to the package DB stack (see #1183 and interpretPackageDbFlags in D.S.Configure).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After trying out the current sandbox support in HEAD I found that I first had to delete my whole user package DB, as the sandboxing support wouldn't install any packages in my sandbox otherwise. We should consider not using the user package DB when using sandboxing, to actually have package be installed into the sandbox.
The text was updated successfully, but these errors were encountered: