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
Date: Fri, 29 Jun 2001 21:46:37 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com, cygwin-patches AT cygwin DOT com
Subject: Re: hierarchy in setup (category stuff)
Message-ID: <20010629214637.A10975@redhat.com>
Reply-To: cygwin-patches AT cygwin DOT com
Mail-Followup-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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i
In-Reply-To: <034701c10106$34f6b6e0$806410ac@local>; from robert.collins@itdomain.com.au on Sat, Jun 30, 2001 at 11:44:30AM +1000

On Sat, Jun 30, 2001 at 11:44:30AM +1000, Robert Collins wrote:
>
>----- Original Message -----
>From: "Christopher Faylor" <cgf AT redhat DOT com>
>
>
>> >> >> Robert, if you are still interested, then I think that this is
>> >definitely the
>> >> >> way to go.  If you have something worth checking in, then please do
>so.
>> >
>> >I'll draw up change log stuff and send something to cygwin-patches... or
>did
>> >you want me to hit CVS directly?
>>
>> Go ahead and check it in.  We can tweak it later.
>
>Committed.
>
>> I was just thinking of using the directories as an organizational method
>> for the packages on sourceware.  The alternative is to somehow get the
>> information into the setup.hint file there or to add some other file to
>> the directory.  That's a lot of work and it's error-prone.  I can easily
>> foresee erroneously having a Development and a Devlopment (misspelled)
>> category if we do this on a per-package basis.
>
>I'm in favour of having that data in the package file itself, and a scanning
>tool that buils setup.ini.

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.

>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?

cgf