Date: Tue, 3 May 2005 11:22:31 -0700 From: Marcel Moolenaar <marcel@xcllnt.net> To: John Baldwin <jhb@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/release/scripts package-trees.sh Message-ID: <20050503182231.GA63201@ns1.xcllnt.net> In-Reply-To: <91d7f4a6ea4f98bead8c37e357d9a63e@FreeBSD.org> References: <200505030419.j434J77M002900@repoman.freebsd.org> <91d7f4a6ea4f98bead8c37e357d9a63e@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 03, 2005 at 09:13:53AM -0400, John Baldwin wrote: > > On May 3, 2005, at 12:19 AM, Marcel Moolenaar wrote: > > >marcel 2005-05-03 04:19:07 UTC > > > > FreeBSD src repository > > > > Modified files: > > release/scripts package-trees.sh > > Log: > > Remove only the packages sub-directory before recreating it. Do not > > remove the whole disc treei structure. This allows one to specify the > > disc trees created by a prior release build (under R/cdrom) as the > > destination without destroying the contents. This better integrates > > with release building and makes further automation easier. > > Hmm, the idea from an automation standpoint is that you'd build the > packages before you built the release, kind of like how we do > 'PREFETCH_DISTFILES' now FWIW. That's typically not how I do it, because it's serial. I typically do things in parallel. This means starting the release build ASAP and work on the packages while the release is building. There is always a lot of uncertainty with packages, so I never let the release wait on it. Also, it's not uncommon for me to have to redo the ISO creation of a release build because I had to make some changes to the packages. The 5.4-RC4 is no different. For the first time all packages were available so it wasn't until now that I ran into the problem that disc2 was overflowing. Depending on how much time I have I either whip up some subset that does fit, or just release the bits and work on it for the next RC (or final release). > Scott had asked if I could modify the > scripts to handle a PKG_TREE that was a URL and maybe use fetch so you > could do something like: That's a good feature. It helps prevent excessive copying from one machine to another. Even if copying from one machine to another is faster, it's almost always better to avoid manual intervention. I would definitely make us of it. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050503182231.GA63201>