Date: Sun, 23 Jul 2000 10:54:03 -0700 From: "David O'Brien" <obrien@FreeBSD.org> To: Steve Price <sprice@hiwaay.net> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/release/scripts print-cdrom-packages.sh Message-ID: <20000723105403.A83797@dragon.nuxi.com> In-Reply-To: <20000723122748.D5963@bonsai.hiwaay.net>; from sprice@hiwaay.net on Sun, Jul 23, 2000 at 12:27:48PM -0500 References: <200007222343.QAA36091@freefall.freebsd.org> <20000722205036.B5963@bonsai.hiwaay.net> <20000722190128.A48362@dragon.nuxi.com> <20000723122748.D5963@bonsai.hiwaay.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 23, 2000 at 12:27:48PM -0500, Steve Price wrote: > Hmm... I suppose if I look hard enough I could find 'people' that > are using nearly every port so they should go on the first disc > too? :) We had a discussion on IRC and attempted to decide how popular and how many people we knew using the ports in this list. Not science, but we need *some* ordering to use if the available package space on disc1 decreases. > Seriously the list of the ports that go on the first disc > should be the ones that people absolutely must have on the first > reboot. The 'nice to haves' go on discs 3 and 4. The first disc > is already overcrowded by KDE and GNOME dependencies and having > 3 versions of the same ftp client seems a needless waste to me. This list + the base bits produced from ``make release'' was only about 550MB. So I don't see why it is a waste as we still need stuff to put on disc1. > BTW, I noticed a couple of more nits that are addressed with the > patch below. > Several ports (including the vim5 port) have dependencies that change > based on the value of a couple of variables that Satoshi and I use to > generate package sets. Can these scripts be committed somewhere? The reason this has happened is because JHB and I needed lists of ports to do RCs. Without this list we have no easy way to produce interm snapshots also. And BSDi had the same problem when we made the FreeBSD Toolkit. It is much harder for us (and I'll assume others) when we (the collective "we") cannot generate the list of disc1 packages in-house. > Also the ksh93 port is RESTRICTED and cannot go on any of the discs. Is the ksh93 port up to date? People have been arguing with me on IRC that Lucent has released the source code and made it free enough we could import into src/contrib/. See http://kornshell.com/ -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000723105403.A83797>