[pkg-GNUstep-maintainers] Re: Bug#256156: How to address the FHS concerns
Matthias Klose
doko@cs.tu-berlin.de
Sat, 26 Jun 2004 06:13:31 +0200
Steve Langasek writes:
> I know my wording in the above email was a bit... convoluted... so just
> to make sure everyone is clear:
>
> - binaries under /usr/lib/<package> are not policy violations if you
> don't intend for people to execute them directly.
> - openapp is a binary that people execute directly, so it must be in
> /usr/bin/; it is a serious bug if they are not.
yes, and these should be fixed (gnustep-make uploaded, new
gnustep-base in new queue).
> - architecture-independent files must be in /usr/share; it is a serious
> bug if they are not.
this last one becomes difficult at the moment. There are certainly
some directories, which can easily be moved to a
/usr/share/System/GNUstep directory, but it get's difficult to split
the '.app' and '.bundle' directories between /usr/lib and /usr/share.
> - These serious bugs, because they appear to be fixable, are not
> ones which I believe should be automatically granted an exemption for
> sarge. However, this is my opinion, not an official position from the
> release team; the only person who gets to pick which bugs are
> ignorable is still AJ. :)
:)
Matthias
PS: Awaiting his mass filing for all python packages...