Your message dated Wed, 14 Sep 2016 20:00:52 +0200 (CEST)
with message-id <[email protected]>
and subject line Re: base: /usr/lib/x86_64-linux-gnu is not FHS-compliant
has caused the Debian Bug report #799318,
regarding base: /usr/lib/x86_64-linux-gnu is not FHS-compliant
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
799318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799318
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: base
Severity: wishlist
Dear Maintainer,
The Linux Filesystem Hierarchy Standard specifies that all platform
libraries must be installed under /usr/lib. See the current FHS standard
document, section 4.6. Subdirectories under /usr/lib are permitted for
individual packages, but not for platforms. Libraries for non-native
platforms should be installed under /usr/lib<platform>, i.e. /usr/lib32.
Debian currently has a /usr/lib/x86_64-linux-gnu under which many,
but not all packages install their libraries. Having some packages
install libraries under /usr/lib and other packages install libraries
under /usr/lib/x86_64-linux-gnu creates confusion and makes it
impossible to detect that a library is installed. Because there
is no standard for the platform name (on other distributions,
x86_64 can be detected as x86_64-unknown-gnu by gcc), it is not
possible to create a general method for library detection, and
requires resorting to either hardcoded dir names per distribution
or a brute force search of the filesystem.
Because Debian is currently the base for most of the major distributions,
and the source of their packages, changing this policy should originate
with Debian. Merging the contents of /usr/lib/x86_64-linux-gnu into
/usr/lib is the policy compliant with the FHS and Debian should lead
by this good example.
-- System Information:
Debian Release: 8.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hello.
[ Sorry for all the time you waited before receiving a reply, there are
not many people answering to bugs in "base", and we really prefer bugs
about real packages and not this "base" pseudo-package ].
On Thu, 17 Sep 2015, Mike Sharov wrote:
> Package: base
> Severity: wishlist
>
> Dear Maintainer,
>
> The Linux Filesystem Hierarchy Standard specifies that all platform
> libraries must be installed under /usr/lib. See the current FHS standard
> document, section 4.6. Subdirectories under /usr/lib are permitted for
> individual packages, but not for platforms. Libraries for non-native
> platforms should be installed under /usr/lib<platform>, i.e. /usr/lib32.
>
> Debian currently has a /usr/lib/x86_64-linux-gnu under which many,
> but not all packages install their libraries.
There is a reason why libraries are put in those platform dependent
places, and it's called "multiarch". You can read about multiarch here:
https://wiki.debian.org/Multiarch
There are a lot of reasons why the new layout is better than the FHS,
so it is very unlikely that we go back to the old way.
You are right that not every package follows the new standard, but
that's because we have not completed the transition to multiarch yet.
> Having some packages
> install libraries under /usr/lib and other packages install libraries
> under /usr/lib/x86_64-linux-gnu creates confusion and makes it
> impossible to detect that a library is installed.
This is generally not a problem because whenever a package needs a
library, it has a Depends on the package containing the library, so
"apt-get install foo" takes care of installing everything which is
necessary for "foo" to work.
(But I guess that your problem is not a Debian package, but something
that you want to make it work on several different platforms).
> Because there
> is no standard for the platform name (on other distributions,
> x86_64 can be detected as x86_64-unknown-gnu by gcc), it is not
> possible to create a general method for library detection, and
> requires resorting to either hardcoded dir names per distribution
> or a brute force search of the filesystem.
>
> Because Debian is currently the base for most of the major distributions,
> and the source of their packages, changing this policy should originate
> with Debian. Merging the contents of /usr/lib/x86_64-linux-gnu into
> /usr/lib is the policy compliant with the FHS and Debian should lead
> by this good example.
As I said before, there are a lot of reasons why we most probably will
not go back to the old standard, so I'm afraid that you will have to
find solutions for whatever problems the new standard creates in your
case.
Please use debian-user if you need help on that.
Thanks.
--- End Message ---
