On Fri, 10.06.11 09:56, Toshio Kuratomi (a.badger@xxxxxxxxx) wrote: > > There are recent packages that choose options 2 && 3 (namely, systemd > > and dracut). > > According to me, guidelines doesn't enforce any of these options, and > > choice is left to packager/reviewer appreciation, though you may > > distinguish an order of precedence. > > > > So, what's the take of my fellow packagers on that particular matter ? > > > Preference-wise, I would say $LIBEXECDIR; settable at build time to > /usr/libexec on Fedora-style distros and /usr/lib on Debian-style distros is > the best method here. Since we're talking scripts (architecture > independent), /usr/share may also make sense but I'm not a big fan of it. > If you can find me the piece of FHS that explicitly allows shell scripts in > /usr/lib I can figure out how that compares to using /usr/lib. What is the benefit of a separate libexecdir? I am actually in favour of dropping libexecdir entirely, as I have trouble seeing what its benefits are. I also believe the distros should not distiungish themselves in this place, as there is no value in doing so here. I think the worst solution is to have each package be configured differently in this regard on the various distributions. Why do we have a separate libexecdir on Fedora, and why do we want to keep it even though everybody else uses libdir? Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
