Re: Splitting in /usr/lib/<arch> and /usr/share
+++ Оlе Ѕtrеісhеr [2014-03-10 11:39 +0100]:
> Andrey Rahmatullin <wrar@wrar.name> writes:
>
> > On Mon, Mar 10, 2014 at 10:54:44AM +0100, Оlе Ѕtrеісhеr wrote:
> >> >> I am packaging some older software (eso-midas, [1]) that installs
> >> >> everything into a common directory (f.e. /usr/lib/eso-midas/). However,
> >> >> the FHS requires that this should be split between /usr/share/ and
> >> >> /usr/lib/<arch>/.
> >> > Nothing forbids you from putting arch-indep files into /usr/lib.
> >>
> >> FHS does: "Miscellaneous architecture-independent application-specific
> >> static files and subdirectories must be placed in /usr/share." [1]
> > Do we enforce this?
>
> "9.1.1 File System Structure
>
> The location of all files and directories must comply with the
> Filesystem Hierarchy Standard (FHS), version 2.3, with the exceptions
> noted below, and except where doing so would violate other terms of
> Debian Policy. [...]" [2]
>
> I would interpret this as: Yes, we do.
And it is good practice. It is attention to detail like this in
packaging that makes Debian a high-quality disto where things generally
work.
But equally if you didn;t bother and just went with upstream's slightly
sloppy install it is unlikly that anyone will come after you with
pitchforks :-)
As this software is stable and the filelist is not going to be changing
all the time I'd list the right files/dirs to copy across to /usr/share
in the packaging and it should require little further attention.
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM
http://wookware.org/
Reply to: