Closed lbdyck closed 1 year ago
Dunno quite what you mean?
The envfile takes the 'install destination' and creates the PATH etc ones?
I've just installed to /prj/git002 and get this:
declare -x MANPATH="/prj/git002/less/share/man:/prj/git002/ncurses/share/man:/prj/git002/bash/share/man:/usr/man/%L:/zdo/conda/envs/ispfgit/man"
declare -x NCURSES_HOME="/prj/git002/ncurses"
It does but those are hardcoded in the envfile instead of generalized. Lionel B. Dyck
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
my point is that if you use this then it is fully generalized and the installation directory can be copied/moved and the active environment can be changed without having to rebuild the envfile.
True,
But i don't feel the installer-one-click should take post processing into account...If one wants it at another location, just run the installer again pointing to the new location... Or run a 'master-sed' to change the envfile :)
The whole idea was/is you install it to where you want it...and gitmaster takes care of it.. :)
Closing for now
Please reconsider - the sample envfile i provided makes the gitmaaster install simple and easy for use with gitmaster install and then to copy/move the installation to somewhere else.
Instead of inserting the install directory in the envfile use $PWD and suffix $PATH/$MANPATH/$LIBPATH etc. rather than using the current values as those can change
this makes it easy to copy the installation