On Wed, Oct 20, 1999 at 05:47:13AM +0000, Alexander Koch wrote: > On Wed, 20 October 1999 11:07:47 +1000, Anthony Towns wrote: > > > Now, who of the ones that *can* change policy is going to do > > > anything on it? Please, can some of those give the many of > > > us an idea of what is the problem or (possibly) what I am > > > getting wrong? > > (a) There's not much point changing policy when the code's not written. > > (b) IIRC the policy proposal *requires* .bz2 compression for all sources, > > rather than just allowing it, which isn't ideal. > The consensus was a different one, mind you. You would be > right here, if not that point (iirc!) was discussed.
The policy weekly summary includes ``I further propose that the use of bzip2 be mandatory for newly uploaded source files''. This has been both seconded and objected to (its Bug#39299). I wouldn't say any sort of consensus has been reached personally. It needs to be rewritten and put forward again. (The README.Debian proposal (Bug#42554) has similar problems) And for some reason I hadn't noticed Chris' code. How embarrasment. Cheers, aj -- Anthony Towns <[EMAIL PROTECTED]> <http://azure.humbug.org.au/~aj/> I don't speak for anyone save myself. PGP encrypted mail preferred. ``The thing is: trying to be too generic is EVIL. It's stupid, it results in slower code, and it results in more bugs.'' -- Linus Torvalds
pgpZ3Nj4DpL3H.pgp
Description: PGP signature
