From owner-freebsd-ports Thu Jul 2 20:36:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02177 for freebsd-ports-outgoing; Thu, 2 Jul 1998 20:36:53 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02171 for ; Thu, 2 Jul 1998 20:36:48 -0700 (PDT) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id NAA01847; Fri, 3 Jul 1998 13:05:54 +0930 (CST) Message-Id: <199807030335.NAA01847@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Atipa cc: dannyman , freebsd-ports@FreeBSD.ORG Subject: Re: New ports scheme In-reply-to: Your message of "Thu, 02 Jul 1998 10:10:23 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Jul 1998 13:05:54 +0930 From: "Daniel O'Connor" Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > maybe we might consider having more than one directory level? like > > net/irc/bitchx, net/ftp/ncftp3, etc ... ? > Sounds good, except that many ports would be their entire "Application > Type" group. I like the idea though; add more sorting heuristics, based 3 > layers deep: Hmm.. if they're all ogoing to be tar.gz's anyway, my not put them in a signle directory and use a simple DB to keep track of them. That way you can have one port in multiple categories.. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message