Re: mass bug gnustep programs: policy violation
On Thu, 24 Jun 2004 15:28:06 -0700, Brian Nelson <email@example.com> said:
> 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?
A long standing bug is nevertheless a bug.
In a medium in which a News Piece takes a minute and an "In-Depth"
Piece takes two minutes, the Simple will drive out the Complex. --
Manoj Srivastava <firstname.lastname@example.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C