Date: Sun, 23 Jul 2000 13:17:30 -0500 From: Steve Price <sprice@hiwaay.net> To: "David O'Brien" <obrien@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/release/scripts print-cdrom-packages.sh Message-ID: <20000723131730.E5963@bonsai.hiwaay.net> In-Reply-To: <20000723105403.A83797@dragon.nuxi.com>; from obrien@FreeBSD.org on Sun, Jul 23, 2000 at 10:54:03AM -0700 References: <200007222343.QAA36091@freefall.freebsd.org> <20000722205036.B5963@bonsai.hiwaay.net> <20000722190128.A48362@dragon.nuxi.com> <20000723122748.D5963@bonsai.hiwaay.net> <20000723105403.A83797@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jul 23, 2000 at 10:54:03AM -0700, David O'Brien wrote: # 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. I agree having some ordering is a good thing. I'm just not convinced that the mechanism used was the best way. Since I haven't thought of a better way, I'll slink away and search for it. :) # 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. How big are the base bits? I have 440MB of packages on the first disc right now. # Can these scripts be committed somewhere? The reason this has happened What scripts? The ones that we (Satoshi and I) use to build packages are already in ports/Tools/portbuild/*. Mine are a slight variant of those (I only have two scripts really) that are tuned more towards my having only one Alpha machine to build packages on. If you are talking about the package splitting scripts, then you can find lots of copies of them in bento.freebsd.org:/b/steve/*. I intend to commit them one day but haven't found the time to clean them up to the point where someone besides me can get them to work. # 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/ My ksh93 port is up-to-date and it still has RESTRICTED in it. If we can distribute these bits now, then someone needs to update the port to reflect it. -steve 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?20000723131730.E5963>