From owner-freebsd-ports@FreeBSD.ORG  Fri Oct 22 16:24:21 2004
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 79E2516A4DF
	for <freebsd-ports@freebsd.org>; Fri, 22 Oct 2004 16:24:21 +0000 (GMT)
Received: from smtp03.mrf.mail.rcn.net (smtp03.mrf.mail.rcn.net
	[207.172.4.62])	by mx1.FreeBSD.org (Postfix) with ESMTP id 5B25D43D1F
	for <freebsd-ports@freebsd.org>;
	Fri, 22 Oct 2004 16:24:21 +0000 (GMT)
	(envelope-from roberthuff@rcn.com)
Received: from 209-6-197-67.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com
	([209.6.197.67] helo=jerusalem.litteratus.org.litteratus.org)
	by smtp03.mrf.mail.rcn.net with esmtp (Exim 4.42 #5)
	id 1CL2DE-0007Sd-PH
	for freebsd-ports@freebsd.org; Fri, 22 Oct 2004 12:24:20 -0400
From: Robert Huff <roberthuff@rcn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16761.13352.825268.411136@jerusalem.litteratus.org>
Date: Fri, 22 Oct 2004 12:24:08 -0400
To: freebsd-ports@freebsd.org
In-Reply-To: <20041022100128.22c34ff6@zork>
References: <20041022074529.GN10363@k7.mavetju>
	<20041022100128.22c34ff6@zork>
X-Mailer: VM 7.17 under 21.5  (beta16) "celeriac" XEmacs Lucid
Subject: Re: ports/www is too full
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Oct 2004 16:24:21 -0000


Robin Schoonover writes:

>  You probably would want to only split into a few medium sized
>  categories instead of a lot of small ones.  Just www, www-client,
>  and www-server for example.

	Isn't there a rule-of-thumb for this kind of human-oriented
subdivision, e.g. "at least three and no more than ten"?


				Robert Huff