On Wed, Apr 26, 2017 at 5:21 AM, Ludwig Nussel <ludwig.nussel@suse.de> wrote:
Michael Matz schrieb:
Hi,
On Tue, 25 Apr 2017, Ludwig Nussel wrote:
I'd personally like this to happen, yeah. It's in line with the original intent of libexec and lib, and that the FHS didn't recognize it was a long standing bug (IMHO, it certainly was a long-standing annoyance :) ).
What's wrong with /usr/lib/name/?
Everything. lib shall not contain executables. lib shall not contain subdirectories. lib shall contain only libraries. lib shall contain _nothing_ on lib64 platforms.
A pretty radical demand. I guess you have technical insight that makes you say that? Even the dynamic linker may read libraries from subdirectories. Also, what about multilib approaches?
IMO /usr/libexec is redundant.
20 years of linux distros doing it wrong by overriding perfectly fine autoconf defaults (caused by the FHS not grasping the concept) makes you think so.
Perfectly fine defaults like /usr/com? :-) Fedora seems to be rather lonely in the Linux world by using libexec.
Fedora isn't the only one using libexec. Mageia does, and several other offshoots of the Red Hat family do. Slackware and its derivatives do too. There used to be more before FHS blatantly ignored the usage of it for many years. Now that it is recognized by FHS, the offense of having things stuffed into /lib can be eliminated. As for /usr/com, I'm not sure whether it's right or wrong, but for better or worse, Linux systems generally assume /usr can be read-only, so shared state information in /usr is wrong, since that assumes a portion of /usr is always writable. And for what it's worth, only autotools assumes shared state is in /usr/com, everything else assumes /var/lib. -- 真実はいつも一つ！/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org