Opened 21 years ago
Closed 21 years ago
#678 closed defect (fixed)
Book's treatment of --libexecdir is bogus
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Book | Version: | CVS |
Severity: | normal | Keywords: | |
Cc: |
Description
LSB compliance implies FHS compliance.
FHS does not mention libexecdir.
Traditional use of libexecdir has been for helper programs used by other programs. These programs were never meant to be in the general $PATH.
We currently do exactly that in a couple of places. I propose we change the affected places to get those binaries out of the $PATH
findutils - --libexecdir=/usr/lib/locate gawk - --libexecdir=/usr/lib/gawk (be careful with current patch) glibc - --libexecdir=/usr/lib (cannot think of anywhere better?) inetutils - (since we now use --disable-servers, libexec has become irrelevant) tar - --libexecdir=/usr/lib/tar
Not urgent at all. Discuss on lfs-dev after release of 5.0.
Change History (14)
comment:1 by , 21 years ago
Priority: | lowest → normal |
---|
comment:2 by , 21 years ago
Status: | new → assigned |
---|
comment:3 by , 21 years ago
Owner: | changed from | to
---|---|
Status: | assigned → new |
comment:4 by , 21 years ago
Status: | new → assigned |
---|
comment:5 by , 21 years ago
comment:6 by , 21 years ago
For correctness I'd then use --libexecdir=/usr/lib even though it's not going to be used.
comment:7 by , 21 years ago
But not in the case of inetutils. It could well be argued those server binaries really should live in /usr/sbin. To be honest, dunno why they are using libexecdir at all :-(
comment:8 by , 21 years ago
True. But as the dir isn't used, it makes more sense (to me anyway) that libexecdir is set to a lib dir rather than a sbin dir. Call it a matter of (personal) taste, but only because nothing actually ends up there. If something would end up there, /usr/lib wouldn't do anymore.
comment:9 by , 21 years ago
rmt installed by tar can be executed independently from tar. --libexecdir=/usr/sbin is more appropriate.
using --libexecdir=/usr/lib for inetutils will clash with BLFS which uses --libexecdir=/usr/sbin.
comment:10 by , 21 years ago
Fair enough. But now the commands are out of sync with BLFS. BLFS installs the servers by default (into /usr/sbin as it should). It would make more sense to me to have it match BLFS, but I don't s'pose it matters much.
comment:11 by , 21 years ago
Let's match BLFS with regards to inetutils. They are the same then and if people ask we can say "because BLFS does it that way and we like to keep commands synced as much as possible" which would be true, people will accept it, easy to deal with.
comment:12 by , 21 years ago
Everything is done with the exception of "tar" -- waiting on answer what to do with "rmt".
comment:13 by , 21 years ago
"rmt" is interesting. I've never used it. But reading the docs, I'm not so sure it is meant to be used directly. It's essentially a "remote tape server" and believe it or not, is meant to be installed as /etc/rmt !! That's how Debian install it too (but as a wrapper script).
It probably matters very little, so we may as well go with what Tush suggested and dump it into /usr/sbin (Debian also put it there).
Probably best to leave inetutils as is. Even tho' we are now using "--disable-servers", if we drop the libexecdir param, we end up with a bogus /usr/libexecdir created.