What do you mean "the executable belongs in /usr/local/bin"? Where an executable belongs is a
matter of site policy. It's the admins of the site that determine that. For all you know, the application is going
to be shared amongst several machines, and it ends up in
/usr/share. Other common places to install third
party software are in /opt and /app.
Abigail | [reply] |
The OP wanted a general place where the executable, modules, and auxilary files should go on a generic general linux install. The advice I gave him (to the best of my knowlage, of course) matches the Linux Filesystem Higherachy Standard, the standard on how linux machines should be orginized in terms of what goes where in the file namespace.
Of course, like everything else, if an individual site doesn't want to follow the standards, it should be free to. An individual installing on such a site shouldn't be using a make install target, and in such a case the OP's question is moot.
Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).
| [reply]
[d/l] |
An individual installing on such a site shouldn't be using a make install target,
Actually, individuals installing on such site only can't use
make install if the package comes with hardcoded
destination targets. Luckely most packages I grab from the net
have been created with metaconf, autoconf
or with ExtUtils:: and are coded sainly. That is, no
hardcoded values that cannot be overriden.
./configure --prefix=/opt/whatever # Look ma, no /usr/local!
make
make install
works fine in many cases, and in my opinion, every software
package should install in similar ways.
Abigail | [reply]
[d/l] |