From owner-freebsd-ports  Fri Jul  7 05:39:20 1995
Return-Path: ports-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id FAA11235
          for ports-outgoing; Fri, 7 Jul 1995 05:39:20 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA11229
          for <ports@freebsd.org>; Fri, 7 Jul 1995 05:39:18 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id FAA05648; Fri, 7 Jul 1995 05:38:54 -0700
Date: Fri, 7 Jul 1995 05:38:54 -0700
Message-Id: <199507071238.FAA05648@silvia.HIP.Berkeley.EDU>
To: jhs@vector.eikon.e-technik.tu-muenchen.de
CC: ports@freebsd.org
In-reply-to: <199507051241.OAA01780@vector.eikon.e-technik.tu-muenchen.de> (jhs@vector.eikon.e-technik.tu-muenchen.de)
Subject: Re: net/ explosion
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: ports-owner@freebsd.org
Precedence: bulk

 * most of those could go in a directory with a nice short name: `web'
 * ( `www' is a term people will stop using in a year or 2,
 * as everyone yawns, & says "yes, obviously its `world wide'" :-)
 * 
 * how about:
 * 	web:
 * 		cern_httpd cern_linemode chimera  lynx tkWWW 
 * 	something_short:
 * 		gn gopher wais  (wwwish ?) xgopher

This sounds like a great idea, I prefer shorter names, but we're
running out of good names quickly.... :<

BTW, what do people think about converting the /usr/ports/* into
multi-level hierarchies?  I personally don't like that idea, 'cause I
won't be able to do things like "grep foo /usr/ports/*/*/Makefile"
anymore but how to reorganize x11/ is giving me headaches....

Satoshi