Re: lintian -- detecting hundrets of bugs within seconds...
> >>"Christian" == Christian Schwarz <email@example.com> writes:
> Christian> 4. We'll provide any easy way to force dinstall to install
> Christian> a package ignoring any errors--without requiring the
> Christian> maintainer to reupload the packages. (Currently, dinstall
> Christian> moves rejected files into REJECTED/, I think. The
> Christian> maintainer can simply move them back into Incoming/ and add
> Christian> a file, say foo.lintian-override, to make lintian ignore a
> Christian> few error messages.)
> This I don't understand. Why are we making it easy to
> distribute packages with bugs? If the errors do not indicate bugs,
> why are they errors?
> why not opt for excellence and not install packages with
> errors? Do we really need mainatainers that can't be bothered not to
> produce bug free packages? It is not as if one can't run lintian
> before uploading.
> confused by all this softness on quality control.
sometimes it is sensible to get even a 'broken' package out
what about adding (or removing) configurability to the
dinstall run of lintian, so that e.g. developer can
override some checks for unstable but not stable or
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to firstname.lastname@example.org .