From owner-cvs-all Sat Mar 27 8:53:44 1999 Delivered-To: cvs-all@freebsd.org Received: from relay.nuxi.com (nuxi.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 2262314F26; Sat, 27 Mar 1999 08:53:43 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.2/8.9.1) id IAA92175; Sat, 27 Mar 1999 08:53:11 -0800 (PST) (envelope-from obrien) Date: Sat, 27 Mar 1999 08:53:11 -0800 From: "David O'Brien" To: Adrian Penisoara Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: ports/news/tin Makefile ports/news/tin/files md5 Message-ID: <19990327085310.A87737@relay.nuxi.com> Reply-To: obrien@NUXI.com References: <199903260752.XAA01445@bubble.didi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Adrian Penisoara on Sat, Mar 27, 1999 at 01:20:16PM +0200 X-Operating-System: FreeBSD 3.1-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk > > Maybe I should add to the handbook that bzip2'd distfiles are to be > > preferred over gzip'd versions.... > > Then please suggest that bzip2 should be integrated in the base > distribution too; would there be licensing problems ? I have thought of suggesting we import Bzip2 (it is under an MIT/CMU/UCB license, not GLP) switch from .tgz for packages to .tbz. But don't care to fight that battle. ;-) I have found the current split of packages between CD #1 and CD #3 to be a pain. Ex: ImageMagic on CD #3 depends on stuff on CD #1, which I never seem to install until ImageMagic demands it. And my two most used ports, vim5 and mutt are on CD #3 and aren't in sysinstall's listing of ports. BUT, I don't have any ideas how to do a better job than Steve did. So I haven't brought this up before. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message