Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID: <035d01c10108$902207c0$806410ac@local>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-developers AT cygwin DOT com>, <cygwin-patches AT cygwin DOT com>
References: <20010621222615 DOT C13746 AT redhat DOT com> <3B3324A7 DOT 49FFC98A AT yahoo DOT com> <054c01c0fbef$5f600e20$0200a8c0 AT lifelesswks> <06a001c0fc51$7a87e210$0200a8c0 AT lifelesswks> <20010629114004 DOT A6990 AT redhat DOT com> <VA DOT 00000842 DOT 01fd0b44 AT thesoftwaresource DOT com> <20010629172912 DOT A8991 AT redhat DOT com> <032001c100fe$d62310c0$806410ac AT local> <20010629205735 DOT K9607 AT redhat DOT com> <034701c10106$34f6b6e0$806410ac AT local> <20010629214637 DOT A10975 AT redhat DOT com>
Subject: Re: hierarchy in setup (category stuff)
Date: Sat, 30 Jun 2001 12:01:22 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
X-OriginalArrivalTime: 30 Jun 2001 01:48:59.0021 (UTC) FILETIME=[D4882BD0:01C10106]


----- Original Message -----
From: "Christopher Faylor" <cgf AT redhat DOT com>

> We already have a scanning tool for this.  It builds setup.ini by scanning
> the directories.
>
> I guess it could open each tar file and look there, too, but that seems
like
> overkill for now.

the advantage of tying the meta data to the files is that local copies of
setup.exe & .ini & packages retain the metadata for new files even if
setup.ini isn't updated. I.e. locally scanned files.

> >This is useful for home users as well, and allows a semi-automated
> >"package verification" so that you don't have to check for Devlopment.
>
> How would this allow for verification?  Would there be a global list
> of accepted categories somewhere?

For ones going onto cygwin.com I think that is absolutely appropriate.
Likewise for dependencies - spelling errors could be fatal(), so the
verifier needs to catalog all the files dependencies in whatever fashion,
and check there are no unsatisfied dependencies.

Rob

> cgf
>