From owner-freebsd-ports Wed Sep 9 12:59:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09909 for freebsd-ports-outgoing; Wed, 9 Sep 1998 12:59:45 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from schultz.io.com (schultz.io.com [199.170.88.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09903 for ; Wed, 9 Sep 1998 12:59:41 -0700 (PDT) (envelope-from jher@schultz.io.com) Received: (from jher@localhost) by schultz.io.com (8.8.8/8.8.5) id OAA00401 for ports@freebsd.org; Wed, 9 Sep 1998 14:59:31 -0500 (CDT) Message-ID: <19980909145931.A29509@io.com> Date: Wed, 9 Sep 1998 14:59:31 -0500 From: jher To: ports@FreeBSD.ORG Subject: suggestion Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I would like to suggest a number of different ports kits. I work for an ISP and I find myself grabbing the entire ports kit, installing it (which takes forever) and then only using about 20% of the kit, if that. What I would like to suggest is twofold: first: how about making tar files of each category? I.E. www.tar, net.tar, etc.. That way I can just update an entire section of my ports collection at once. second: combine said categories into larger groups like "foreign.tar" which has german, vietnamese, korean, etc.. in it.. "webserver.tar" which has say net.tar, www.tar, shells.tar, lang.tar, etc.. This would make life a hell of a lot earlier for folks like myself. Also, why the heck does the default install of freebsd 2.2.x and 3.x have perl4 as the default perl instead of perl5? Everytime I do an upgrade it breaks my setup.. -- Today is Boomtime, day 33 in the season of Bureaucracy, 3164. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message