-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
[proposal]: Add custom paths/settings to environment modules #1109
Comments
I like it! |
Can I suggest : modules:
...
jdk:
set_env:
- JAVA_HOME: {prefix}
foo:
prepend_path:
- BAR: {prefix.lib}
append_path:
- BAZ: {prefix.include} in that way you may use python string formatting capabilities out of the box 😄 |
@mwilliammyers I have received a bunch of user feedback for our modules and I'll need to generate something like what you propose, with the only difference that I'll need to permit some token expansion also on the keys, e.g. : modules:
prefix_inspections:
'':
- '{name}_ROOT'
tcl:
all:
environment:
set:
'{name}_FOO': '{ver}' Did you start already working on this? In case, would it make sense to you to work together in #1135 ? @tgamblin ? |
@alalazo sorry this one/your most recent comment slipped by me. I am currently revamping the opencv package because I need to get that installed. I am almost done with that and so I would be happy to work on this with you, if it is not too late. |
I think you can already add custom paths eg. export
PYTHONHOME
to a generated environment module using this method inpackage.py
but it would be nice to be able to not have to modify thepackage.py
file or override it with another local package.I am thinking something like this for the
modules.yaml
config:Where you can reference any of the prefix attribute variables listed here.
The text was updated successfully, but these errors were encountered: