-
Notifications
You must be signed in to change notification settings - Fork 212
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
Add shell.package_path
setting for package.path
defaults
#1662
base: mc-1.20.x
Are you sure you want to change the base?
Conversation
Related discussion where this was already denied #739 |
I'm thinking of this more from a user-oriented perspective, where the user gets to determine what their own path is (and hopefully a program/package manager would respect the user's wishes), rather than as something for programs to abuse for their own paths. Of course, you can't force programs to not do bad things, but the way things are right now makes it very difficult to have common libraries for your own programs, and I think this is the simplest and most minimally invasive way to fix it. OTOH, maybe the reason CI failed is exactly why this is a bad idea. 🙃 If a global setting is a bad idea, then the next best way to resolve this issue is to add inheritance. This keeps the idea of using wrapper programs, but makes it a bit more flexible by allowing the original program to be run with |
Would |
This PR simply adds a new setting called
shell.package_path
, which stores the defaultpackage.path
value. This allows users and programs to easily add global library paths without having to overridecc.require
. For instance, this can be used by package managers to add a central directory for shared libraries, instead of requiring programs to have their own copies of common software. The default settings will remain the same, andpackage.path
changes in programs won't affect anything else globally.