Date: Wed, 4 Feb 2004 02:52:07 +0100 From: Melvyn Sopacua <freebsd-questions@webteckies.org> To: freebsd-questions@FreeBSD.org Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: 4 CD ISOs for 5.2 ? Message-ID: <200402040252.18639.freebsd-questions@webteckies.org> In-Reply-To: <40201EA3.2040106@freebsd.org> References: <016f01c3ea33$182e1210$1b01a8c0@itg.ti.com> <20040203213646.GB9261@xor.obsecurity.org> <40201EA3.2040106@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Boundary-02=_SBFIAvUUr462Sm3 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 03 February 2004 23:20, Scott Long wrote: > Kris Kennaway wrote: > > On Tue, Feb 03, 2004 at 04:52:14PM +0100, Melvyn Sopacua wrote: > >>On Tuesday 03 February 2004 13:41, Kris Kennaway wrote: > >>>Only the first 2 CDs are made available on the FTP site. The other > >>>two contain a subset of packages; the full set of packages is > >>>available on the FTP site, just not in ISO format. > >> > >>Regarding the first cd: > >>make release > >>only creates a 'mini-install', not the 600M iso that is on the site. Th= is > >> one misses perl for one and some dependencies fail. > > > > AFAIK packages are included by hand. > > Correct. We've talked about enhancing the scripts so that this gets > included automatically, but it can be problematic since the source > location of the packages might be unknown at the time of the build. Do you mean the distfiles here, or the resulting packages? If talking about the packages, isn't it as simple as moving the=20 $CHROOT_DIR/usr/ports/packages into $CHROOT_DIR/R/cdrom and using a similar= =20 approach as portupgrade? Otherwise an ls */*/*.tbz should print a workable= =20 list. If the distfiles, then one can advise in the release manpage, to do: /usr/src/release/scripts/print-cdrom-packages.sh 1 | xargs portinstall=20 =2D-fetch-only and then proceed with RELEASEDISTFILES argument. Life would be a lot simpler if portupgrade was moved into base :) > >>I followed release(7) and the docs on the site - how can I create the > >>"official" disc1 and can that be done, without restarting the entire ma= ke > >>release process? > > > > I don't know more specifics. > > > > Kris > > The 'rerelease' target will start up a build where it left off, without > cleaning the CHROOTDIR area first. Hmm - this is much clearer then: "Assumes that the output of a release build has been manually modified, and= =20 performs the minimal number of steps to rebuild the release using the=20 intermediate output of the previous ``make release''." > The RELEASENOUPDATE flag will=20 > prevent the scripts for doing a cvs update on the tree. Both of these > are useful for restarting a paused build. Also, depending on what > actions you want to modify or restart, you might need to remove certain > makefile marker files at $CHROOTDIR/usr/obj/usr/src/release. Thanx, I'll see how things go. =2D-=20 Melvyn =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D =46reeBSD sarevok.webteckies.org 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Wed Ja= n 28=20 18:01:18 CET 2004 =20 root@sarevok.lan.webteckies.org:/usr/obj/usr/src/sys/SAREVOK_NOAPM_NODEBUG = =20 i386 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D --Boundary-02=_SBFIAvUUr462Sm3 Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAIFBSOv9JNmfFN5URAg/kAJ0fUZPVHAs3NB4HunThGFDujpgfqACgwwgR t89Ga40KS8BCz9+i4Ki4F3s= =EHnl -----END PGP SIGNATURE----- --Boundary-02=_SBFIAvUUr462Sm3--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200402040252.18639.freebsd-questions>