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: <034701c10106$34f6b6e0$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: <04e801c0faa2$f9008260$0200a8c0 AT lifelesswks> <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>
Subject: Re: hierarchy in setup (category stuff)
Date: Sat, 30 Jun 2001 11:44:30 +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:32:07.0256 (UTC) FILETIME=[79791580:01C10104]


----- 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. 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. I don't think I'll have time to address that just yet :], but it
is a standard mechanism for .deb, .rpm, and .pkg files..

> As far as the layout on the user's side, I don't really care, except
> that we could almost forgo setup.ini completely and just rely on the
> directory layout for "Install From Current Directory".
>
> The next thing we have to do is add descriptions.  That will involve
> another chooser change.

pick_line:: paint and the package_headers global are all that needs
modification for a bare bones "add description column after the package name
column".

Rob

>
> cgf
>