On Sun, Aug 29, 2004 at 10:47:48PM +0200, Jeroen van Wolffelaar wrote:
> Diverting to lintain-maint, where this is more appropriate...
Just subscribed, for a better understanding of the lintian philosofy
(this thread started on -mentors)
> On Sun, Aug 29, 2004 at 10:26:13PM +0200, Geert Stappers wrote:
> > On Sun, Aug 29, 2004 at 07:26:35PM +0200, Jeroen van Wolffelaar wrote:
<snip/>
> > > Regarding this check, see /usr/share/lintian/checks/huge-usr-share, and
> > > note that due to its new, experimental nature, it is only displayed when
> > > you enable informative checks, by means of lintian -I.
> >
> > Hey a -I flag, lets try it:
> >
> > $ lintian -I conglomerate_0.7.14-1_powerpc.deb
> > I: conglomerate: arch-dep-package-has-big-usr-share 4448kB 86%
> >
> >
> > Okay, I found what I was looking for ....
> > What is a constructive way to solve our different expections
> > of _all_ checks and "forceing hus check" versus the -I flag?
>
> Dunno, -C et al are IMHO to be discouraged, are only for very rare,
> specialized uses. I'm actually in favour of dropping them from the
> --help, and in manpage, maybe even move all that advanced stuff to a
> different manpage/chapter. Regular maintainers shouldn't ever need that
> option, it's only needed if you're doing some QA stuff or mass-checking,
> and then you need to read the code anyway...
>
> > (next is dutch, native language for me and probably also for Jeroen
> > Wat is een opbouwende manier om ons verschil in verwachtingen
> > bij _alle_ test en de "geforceerde hus test" tegenover
> > de -I optie op te lossen?)
>
> I understood the English part fine :), indeed, Dutch is my native
> language, as you have guessed from my .nl email.
( something personal in dutch:
Ik was aangenaam verrast toen je op developers@debian.nl
vertelde dat je de maintainer van lintian bent.
Ik wist dus dat je nederlands kunt, ik weet echter ook
dat ik wel eens duw op plek waar het pijn doet.
Niet om het pijn doen, maar om duidelijk te krijgen
waar de pijn zit.
Genoeg goede bedoelingen vertelt, ik ga je vertellen dat
ik je voorstel een minder voorstel vind )
With all respect, but I think you did not understand me.
When the manual pages says all checks, I expect _all_ checks.
When I say "-C hus", I want to check for a huge /usr/src
Our disagreement possible about this part from lintian manual page
Behaviour options for lintian.
-I, --display-info
Display informational ("I:") tags as well. They are normally
suppressed.
and the especial "normally suppressed".
What was the idea of doing some checks and then suppress them?
Please don't drop "-C check". Not from --help, the manual page
nor from the code. Provide a tool for both regural users
and users that are doing mass QA checks. A split in the tool set
will do harm I my opinion. (QA reporting "you forget that" and
regulars users replying "How can I check it when I have made
a change on that?")
Allow -C CHECK to show output, even when informational ("I:") is suppressed.
Cheers
Geert Stappers
Attachment:
pgpHAdRYqBXMs.pgp
Description: PGP signature