Re: lintian -- detecting hundrets of bugs within seconds...
- To: Christian Schwarz <firstname.lastname@example.org>
- Cc: Debian Development <email@example.com>
- Subject: Re: lintian -- detecting hundrets of bugs within seconds...
- From: Joey Hess <firstname.lastname@example.org>
- Date: Tue, 27 Jan 1998 15:58:02 -0500
- Message-id: <19980127155802.27006@kite>
- In-reply-to: <Pine.LNX.3.96.980125231316.9061B-100000@monet>; from Christian Schwarz on Sun, Jan 25, 1998 at 11:55:34PM +0100
- References: <Pine.LNX.3.96.980125231316.9061B-100000@monet>
Christian Schwarz wrote:
> Ok, now to the checks: Each check script reports lines of the following
> N: <verbose text for the user>
> W: <pkg>: <tag> <arguments>
> E: <pkg>: <tag> <arguments>
> E: logwrites: pkg-without-shlibs-has-shlibs-control-file
> -> Policy violation: Package `logwrites' does not contain any shared
> libraries, but has a `shlibs' control file.
I think it'd be useful to include in the output a reference to the
appropriate section of the policy manaul. This makes it easy to go read the
policy, without a long explination. (Also, lose the '-'s, they make it hard
BTW, I was earlier looking into making the policy manual a literate
programming document that generated a lint checker and the policy manual. I
never got very far with it, but I wonder if you've givn any thought to that?
The idea is when you write policy, you'd also write the code fragements
that check policy, as part of the same document, which keep things from
getting out of sync, and then you process it through a program that splits
the policy text and the code. I was looking into making a SGML DTD that
added some tags to enable this. Unfortunatly, I ran out of time to learn
see shy jo
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to email@example.com .