Quote:
Originally Posted by
rugdog
i there's little you can do to prevent your users to use:
./configure --prefix=/some/path
or ./configure alone...
wouldn't be easier to instruct your users to alwasy use --prefix=$HOME/apps/metapackage/packagename/packageversion ?
perhaps you could add in the .profile a shortcut for that like:
export PREFIX=$HOME/apps/metapackage/packagename/packageversion
so they can issue
./configure --prefix=$PREFIX
I would actually count on the users getting this part wrong almost consistently.
Sorry, but that is what I have to say about the users.
However, what I can count on them is saying some sort of command like this -
python update_packages.py -p package_name -v version# -m metapackage_name -c
(-> -c equals 'create')
-and having this in their config file for the package:
configure (or for perl packages: perl Makefile.pl)
make
make install
Paths are something they will probably be sure to get wrong.
Thanks guys.
---------- Post updated at 02:10 PM ---------- Previous update was at 02:08 PM ----------
To add to that, I am have currently just made sure to send all commands through a python function which does this check for me. But if the use of commands gets widespread through the package manager program, then this could add more redundancy, than say setting something on the environment level.