On Fri, Dec 04, 2009 at 09:42:32PM +0100, Cristian Morales Vega wrote:
2009/12/4 Philipp Thomas <pth(a)suse.de>de>:
* Vincent Untz (vuntz(a)opensuse.org) [20091204
Hrm, I'm talking about libexecdir vs libdir,
not libdir vs datadir :-)
Me too :) But I guess I should have phrased it better. But I think I'd
better study the FHS again before I say more because as far as I remember,
it says nothing about libexecdir.
FHS says: "/usr/lib includes object files, libraries, and ***internal
binaries that are not intended to be executed directly by users or
That is the definition of libexecdir ("The directory for installing
executable programs to be run by other programs rather than by users")
GNU says libexecdir should normally be $(exec_prefix)/libexec, that
enters in contradiction with FHS.
GNU and FHS is not entirely compatible, but Linux distributions
generally tend to follow FHS, which has been AFAIK designed in the
glorious past to align all modern UNIXes together in this regard.
FHS has no libexec and *generally* uses /usr/lib for this purpose.
I'd expect SUSE to follow FHS like other Linux distributions (Debian
is especially strict about this, and libexec in particular which is
a prominent point of content), but of course this is up to our core
packagers to decide - one could also say that it's too a minor point
to waste time on.
I was not able to quickly google out exact technical reasons for not
including libexec, but I found some political ones...
Petr "Pasky" Baudis
A lot of people have my books on their bookshelves.
That's the problem, they need to read them. -- Don Knuth
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org