-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
Deprecate propagatedUserEnvPkgs #43049
Comments
From the website:
Given that and your information, a deprecation is the least that could be done. Straight up deletion of |
Alternatively, it wouldn't be hard to add support for |
Is it worth supporting though? It seems like something that will hit you in a lot of different ways - not just Also |
Note there are also some occurrences of I like to see this removed, because I think we should be able to run everything directly from the store. At the same time, I know some people like to be able to install individual packages and let them be discovered automatically, in which case this attribute is sometimes needed for dependencies. |
In my experience, |
I'm not sure symlinking is better than propagating. For example, if I install package A (which symlinks parts of B) and package B, then the user environment builder might fail due to collisions between A and B. (Not entirely sure about that though - it might be that the collision check is on canonicalized symlink targets.) Also, symlinking is potentially more expensive (since you have to symlink an unbounded number of files). |
Issue description
With Nix 2.0 having the
nix run
command, we can no longer assume that packages will be installed by users before being run. It seems like this is a good opportunity to officially deprecatepropagatedUserEnvPkgs
as it only works when something is installed. Otherwise people are encouraged to utilize this for certain things, where they should instead use makeWrapper.Also it would be nice to get rid of Nix's support for
nix-support/propagated-user-env-packages
but I am much more concerned about Nixpkgs use of it.The text was updated successfully, but these errors were encountered: