On Tue, 2005-10-18 at 23:42 -0600, Archaic wrote: > I like /usr/lib/packagename. Either way, this will have a far reaching > outcome and should be discussed by both lfs and blfs.
I'm not sure that there is a real effect where these programs are installed. If you pass --libexecdir=/someplace/nobody/expects the programs will still be found by the library or program looking for it. This is handled by the configure/make/make install process. And internally registered to the calling process. These programs do not need to be in the path, nor should they be executed by the root user. Therefore /usr/sbin is probably not the right place. > Ultimately, it is > just a philsophical decision with no real technical difference. What's > the FHS say? The FHS says that programs in /usr/sbin should be non-essential programs designed to be run by the root user. So, /usr/sbin doesn't seem correct according to the FHS. FHS says /usr/libexec is just fine. It also says that /usr/lib/packagename is just fine. I'm inclined to lump all these types of programs in /usr/libexec instead of a bunch of unneeded, though descriptive, directories. -- Randy rmlinux: [bogomips 3923.96] [GNU ld version 2.16.1] [gcc (GCC) 4.0.1] [GNU C Library stable release version 2.3.5] [Linux 2.6.12.6 i686] 00:52:09 up 10 days, 10:01, 9 users, load average: 0.00, 0.02, 0.12 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
