Currently EB refuses to install software if the $EBROOTWHATEVER variable for that package is set. I've encountered an issue when dependencies are also loaded ($PYTHONPATH gets unset by EB, so on packages that depend on Python, the Python module does't get reloaded, but $PYTHONPATH has been unset).
I think it makes sense what Kenneth proposed in an email exchange, and extended the check to dependencies.
There are a few questions on how to better tackle this:
- Check for direct dependencies, full dependency tree, or something in between?
- Reject to install or display a big warning?
- Make it overridable (via
--ignore-modules-loaded-check for instance) or not?
My preferences would be: full dependency tree, reject, overridable.
Thoughts?
Currently EB refuses to install software if the
$EBROOTWHATEVERvariable for that package is set. I've encountered an issue when dependencies are also loaded ($PYTHONPATHgets unset by EB, so on packages that depend on Python, the Python module does't get reloaded, but$PYTHONPATHhas been unset).I think it makes sense what Kenneth proposed in an email exchange, and extended the check to dependencies.
There are a few questions on how to better tackle this:
--ignore-modules-loaded-checkfor instance) or not?My preferences would be: full dependency tree, reject, overridable.
Thoughts?