Re: API freeze release ... status so far.

Section 4.5 of the FHS:
/usr/lib includes object files, libraries, and internal binaries that are not intended to be executed directly by users or shell scripts.

and Section 4.8:
The /usr/share hierarchy is for all read-only architecture independent data files. (...) thus, for example, a site with i386, Alpha, and PPC platforms might maintain a single /usr/share directory that is centrally-mounted.

I think one should read "Architecture independant" as "if it's not an executable and it isn't compiled for a specific architecture" If what you're telling me is that there might be a .pc for a library available one arch, and not for the other, I could argue that the same problem would happen if 2 versions of one application have different layouts under their /usr/share/application dir (and different versions are available on the platforms), or if a bonobo component is available on one platform and not the other (/usr/share/oaf)

Maybe that's just me being picky...


Havoc Pennington wrote:

Bastien Nocera <hadess hadess net> writes:
Talking about which... Why is it that the .pc files get installed
under $(libdir)/pkgconfig instead of $(datadir)/pkconfig ?
Architecture independant files are supposed to be under share/ not
lib/ afaik.

.pc files need not be architecture-independent. Therefore they
accompany the library itself in libdir.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]