Re: mass bug gnustep programs: policy violation
Manoj Srivastava <firstname.lastname@example.org> writes:
> On Thu, 24 Jun 2004 09:15:20 +0200, Andreas Barth <email@example.com> said:
>> This is exactly what's keeping sarge non-releasable: We change core
>> functionality far too often. _Please_ don't do it. Please just
>> accept that we are near a release, and that we don't want to change
>> basic functionality now.
> Hopefully the desire to release immediately has not thrown
> every other consideration out of the window, like standards
> conformance, quality, and policy compliance, and so on, that makes
> Debian a desirable OS.
> We used to not release until we were ready. And this
> violation of the FHS seems like an indication that perhaps gnustep
> packages are not yet ready -- do you have any arguments as to why we
> must release these packages before they match our policies?
Because they've been packaged this way for a long time and work the way
they are now?
(I'm indifferent to the outcome of GNUStep in sarge--just pointing out
the other side of the argument.)
You win again, gravity!