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

Re: where do NEW packages go?



On Sun, 19 May 2002, Steve Langasek wrote:

> On Sat, May 18, 2002 at 11:49:45PM -0500, Adam Heath wrote:
> > On Sat, 18 May 2002, Branden Robinson wrote:
>
> > > > Why not just use /libexec, for hurd, and be done with it?  Why force the rest
> > > > of Debian to require use of it?
>
> > > As I understand it, that's all they're asking for.  But Debian Policy
> > > says "follow the FHS", and {/usr,}/libexec doesn't.  And some non-Hurd
> > > Debian developers are sufficiently enamored of the concept of Policy as
> > > universally applicable without exception that it feels like anti-Hurd
> > > discrimination to some people.
>
> > I don't see that adding /libexec on hurd is a violation of policy.
>
> It most definitely would be.  All files that the Hurd port wants to put
> in {/usr,}/libexec are required by the FHS to be placed in
> subdirectories under /usr/lib.  Because Debian Policy says we must
> follow the FHS, it's pretty clear that this is not currently acceptable.

Hint: policy is wrong, so ignore it here.  Then, you'll have no problems.

Policy is not a stick used to beat people with.  It's a guideline.  Policy has
never said it was 100%.

In this event, policy is behind the times.  So, you implement
something(/hurd|/libexec), and when things are working with your
implementation, policy is modified to document and describe the
implementation.

Policy is never modified first.


-- 
To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: