You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
will lead to a wrong and empty MODULESHOMES (which seems not to be used by the tool itself, but is mainly used as $MODULESHOMES/init/<init-skript> by external scripts).
furthermore libdir, libexecdir,datarootdir,mandir,docdir,vimdatadir have to be manually prefix (with /usr/local) since they will be install to the wrong place (usr/local/etc) otherwise
an alternative to facilitate compability to all (but in my eyes stranges/broken setups) would be to add a --moduleshome option with the parentdir of the initdir as default.
To clarify a bit more: the main compability I would like to keep is for users that had a local installation (default options -> /usr/local/Modules) and switch to a packaged installation.
However for a general packaging guideline is to have configuration files in /etc and binaries, libs, etc. in /usr …
Will add a configuration option home that will control the setup of the MODULESHOME variable. And a ./configure option --with-moduleshome to enable the setup of the right value at installation time.
As initially described on #287
Following a typical linux layout, e.g.
will lead to a wrong and empty
MODULESHOMES
(which seems not to be used by the tool itself, but is mainly used as$MODULESHOMES/init/<init-skript>
by external scripts).Suggested patches:
Originally posted by @xdch47 in #287 (comment)
Without this fix, the prefix option is (from my point of view) is broken.
it feels pretty odd/wrong to have
furthermore libdir, libexecdir,datarootdir,mandir,docdir,vimdatadir have to be manually prefix (with
/usr/local
) since they will be install to the wrong place (usr/local/etc
) otherwisean alternative to facilitate compability to all (but in my eyes stranges/broken setups) would be to add a --moduleshome option with the parentdir of the initdir as default.
Originally posted by @xdch47 in #287 (comment)
To clarify a bit more: the main compability I would like to keep is for users that had a local installation (default options ->
/usr/local/Modules
) and switch to apackaged
installation.However for a general packaging guideline is to have configuration files in
/etc
and binaries, libs, etc. in/usr
…Originally posted by @xdch47 in #287 (comment)
The text was updated successfully, but these errors were encountered: