Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <017d01c16f26$f05cf9b0$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin AT cygwin DOT com>
Subject: Re: new site for my ports is up 
Date: Sat, 17 Nov 2001 16:15:56 +1100
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 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-OriginalArrivalTime: 17 Nov 2001 05:14:03.0645 (UTC) FILETIME=[AC7DCAD0:01C16F26]

My mail is currently broken inbound... so I'm replying from the list
archives..

===
Ah!  Sorry about that.

The idea of putting things under categories was something that I
originally proposed but I wasn't entirely sure that it was ok.

I wonder if we shouldn't just dispense with any hierarchy at all and put
all of the packages in their own subdirectory, like ftp.gnu.org?

cgf
===

A flat structure may not scale efficiently on some systems. I was (for
obvious reasons I hope) against a category based directory structure,
but pretty much anything else should be fine :].

As for putting multiple pacakges in the same dir - yes thats good but
let me get setup.hint subsumed into the package file first...

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/