Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Date: Mon, 2 Jul 2001 23:43:27 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com, cygwin-apps AT cygwin DOT com
Subject: setting up category info
Message-ID: <20010702234327.A10335@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com, cygwin-apps AT cygwin DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i

In keeping with the recent discussion about setting up category info in
setup.ini, I'd like to propose a three-pronged method for dealing with
the problem.

1) Reorganize the "contrib/latest" directory via category name.  We can
   use this, for now, to get the category types for setup.ini.

2) The program that understands setup.hint currently understands the following
   keywords:

  skip
  prev
  curr
  test
  sdesc
  ldesc

  I will be also adding:

  category
  depends

   with, I hope, obvious meanings.

3) I think that we should start adopting the use of a CYGWIN.PKG file
   in our distributions.  This file will essentially be a setup.hint file,
   although an external setup.hint will take precedence.

Step 1 is only a stopgap measure but I think it makes sense to start
organizing the tar files in this way, anyway.  Especially since contrib
and latest have become meaningless.

Make sense?

cgf