Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Message-ID: <0ad501c1a07f$c15af920$0200a8c0@lifelesswks>
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Michael A Chase" <mchase@ix.netcom.com>,
   "Charles Wilson" <cwilson@ece.gatech.edu>,
   "Joshua Franklin" <joshuadfranklin@yahoo.com>
Cc: <cygwin@cygwin.com>
References: <20020117190003.69826.qmail@web20009.mail.yahoo.com> <3C473531.7020905@ece.gatech.edu> <070f01c19fda$d81f4760$0200a8c0@lifelesswks> <000101c19ff6$74c36c20$ec00a8c0@mchasecompaq>
Subject: Re: Package Lint
Date: Sat, 19 Jan 2002 11:25:09 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

----- Original Message -----
From: "Michael A Chase" <mchase@ix.netcom.com>


> I have been away for a while and would be interested in working on a
package
> lint as a way of getting back in the loop.  What would you like it to
check
> first?
>
> My first thought would be to make it a Perl script.

I'm open on this. I expect at some point to produce a setup.ini linter,
and that could be called from a perls script easily enough. (We should
have the same parser code reused, to prevent syncronisation errors).

> Likely features:
> 1. No /usr/info/dir allowed.
> 2. Syntax check setup.hints.

upset is perl now, I'd suggest you extend upset.
Also, for efficiency, write a flag - same foobar.checked - when you
check a file (be it a setup.hint or package), and only recheck if the
file is newer than the flag.

This is because untarring a 100Mb of archives every upload is a waste of
CPU time - and the server is quite loaded already.

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/