Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Sat, 17 Nov 2001 12:32:57 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: new site for my ports is up Message-ID: <20011117173257.GB23168@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <017d01c16f26$f05cf9b0$0200a8c0 AT lifelesswks> <20011117172920 DOT GA23168 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011117172920.GA23168@redhat.com> User-Agent: Mutt/1.3.23.1i On Sat, Nov 17, 2001 at 12:29:20PM -0500, Christopher Faylor wrote: >On Sat, Nov 17, 2001 at 04:15:56PM +1100, Robert Collins wrote: >>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... > >No. No multiple packages in the same directory. Every package gets >their own directory. Just to clarify: By "no multiple packages", I mean that I don't want to see (to pick an extreme example) ash-blah.tar.bz2 and binutils-blah-tar.bz2 in an ash+binutils directory. cgf -- 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/