From owner-freebsd-ports@FreeBSD.ORG Fri Oct 22 16:24:14 2004 Return-Path: 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 CCEE816A4CE for ; Fri, 22 Oct 2004 16:24:14 +0000 (GMT) Received: from maxlor.mine.nu (c-213-160-32-54.customer.ggaweb.ch [213.160.32.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8339A43D2F for ; Fri, 22 Oct 2004 16:24:14 +0000 (GMT) (envelope-from benlutz@datacomm.ch) Received: from localhost (localhost [127.0.0.1]) by maxlor.mine.nu (Postfix) with ESMTP id 3A80822D for ; Fri, 22 Oct 2004 18:24:13 +0200 (CEST) Received: from maxlor.mine.nu ([127.0.0.1]) by localhost (midgard [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 71346-06 for ; Fri, 22 Oct 2004 18:24:11 +0200 (CEST) Received: from merlin.intranet (merlin.intranet [10.0.0.16]) by maxlor.mine.nu (Postfix) with ESMTP id 9200418F for ; Fri, 22 Oct 2004 18:24:11 +0200 (CEST) From: Benjamin Lutz To: freebsd-ports@freebsd.org Date: Fri, 22 Oct 2004 18:24:08 +0200 User-Agent: KMail/1.7 References: <20041022074529.GN10363@k7.mavetju> <41791AF7.2050009@vonostingroup.com> In-Reply-To: <41791AF7.2050009@vonostingroup.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1409530.I7DKK8T8TG"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200410221824.12294.benlutz@datacomm.ch> X-Virus-Scanned: by amavisd-new at maxlor.mine.nu 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Oct 2004 16:24:14 -0000 --nextPart1409530.I7DKK8T8TG Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline >Ports/www is too full: 755 ports. There's even worse categories than www: /usr/ports# for f in `make -V SUBDIR`; do echo -n "$f\t"; ls $f | wc -l;=20 done | sort -k 2 [snip dirs with less than 200 entries] x11-toolkits 211 editors 215 math 249 x11 266 print 270 lang 281 databases 335 japanese 430 misc 441 security 463 audio 471 mail 480 sysutils 511 graphics 526 games 644 textproc 679 www 756 net 796 devel 1404 Why does it matter that some dirs are rather large? Personally I'd rather=20 be able to guess where a port resides (which is harder with more=20 categories), than to have an "ls /usr/ports/www" fit onto a single=20 screen. There will be 12000 ports soon, imo splitting directories all the time is=20 not good solution to the problem you're having (getting to that), nor is=20 adding another level of depth in the file system hierarchy (and having=20 varying depths is even worse). Reading between the lines, the problem you're having is that the ports=20 aren't well enough categorized at the moment. How about borrowing an idea=20 from some of the knowledge databases, and using keywords to mark ports?=20 Eg, instead of creating a www-server category, the apache port could be=20 marked "server www". linux-opera could be market "binary browser client=20 linux www" or something like that. The number of keywords that exist as well as the number of keywords=20 assigned to a single port could then be much more easily changed and=20 updated. Of course, there'd need to be a program for filtering the ports=20 by keyword, but it'd be trivial to write one or to put this functionality=20 into make search. Just some more ideas from an user :) Greetings Benjamin --nextPart1409530.I7DKK8T8TG Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBeTQsgShs4qbRdeQRAqDSAJ4+IF0BQ6Ex5C+veuxUJ+/kmydFjQCdHxxG aXVO3osPt/4nhd2n9o/6a2Q= =lIT1 -----END PGP SIGNATURE----- --nextPart1409530.I7DKK8T8TG--