On Sat, Nov 23, 2002 at 09:52:36PM +0100, Jelmer Vernooij wrote: > > >There's already a directory for architecture specific library files - > > >libexec. We haven't needed to use this so much before so it probably > > >isn't supported in configure.in. How about $(LIBEXECDIR)/modules as > > >a location for the vfs modules? > What's the exact difference between lib and libexec? The FHS doesn't > seem to have libexec and some other OS'es seem to put executables that > are not to be called directly by users in libexec.
This is the distinction between the two as I understand it, and it's certainly been the GNU explanation for the difference. The FHS folds libexec back into lib, however. Since /usr/libexec/ contains only subdirectories (in theory), this isn't much of a problem either way. I fall on the FHS side of the fence, if only because it makes tab completion easier. ;) > > I would preferr to use LIBDIR/samba , LIBDIR/samba/modules , > > LIBEXECDIR/samba or LIBEXEC/samba/modules (but I would like one of the > > first two) > Most programs with modules put them in some directory in > /usr/lib/<name-of-program> - that would be the best place imho, since the > plugins are really just libraries that are only loaded 'manually'. > > I also don't like the valid.dat , upcase.dat, lowcase.dat installed to > > LIBDIR they should go to LIBDIR/samba/ or CONFIGDIR/ (we should always use > > the subdir samba, exept BINDIR and SBINDIR) > valid.dat, upcase.dat and lowcase.dat should be in $(PREFIX)/share/samba (for FHS at > least) Correct. There's also the dichotomy between installing samba into a private heirarchy (/usr/local/samba/share/), and installing it as part of the system (/usr/local/share/samba/ or /usr/share/samba/). This is the problem with saying "we should always use the subdir samba", because there are still unbelievers[1] who don't want this. :) -- Steve Langasek postmodern programmer [1] <wild gesticulation in the direction of Slackware> :)
msg04587/pgp00000.pgp
Description: PGP signature
