Date: Mon, 29 Apr 2002 16:46:47 +0300 From: Ruslan Ermilov <ru@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, Makoto Matsushita <matusita@jp.FreeBSD.org> Subject: Re: cvs commit: src Makefile Makefile.inc1 src/etc Makefile src/ Message-ID: <20020429134647.GA52838@sunbay.com> In-Reply-To: <XFMail.20020429085650.jhb@FreeBSD.org> References: <20020427143440.GF35685@sunbay.com> <XFMail.20020429085650.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Apr 29, 2002 at 08:56:50AM -0400, John Baldwin wrote: >=20 > On 27-Apr-2002 Ruslan Ermilov wrote: > > On Fri, Apr 26, 2002 at 11:10:22PM -0400, John Baldwin wrote: > >>=20 > >> On 27-Apr-2002 Makoto Matsushita wrote: > >> >=20 > >> > Correct typo.. > >> >=20 > >> > matusita> Does this mean "make release" procedure can't use any tool= s that > >> > "make release.X (where X =3D 1..9)" > >> >=20 > >> > *** > >> >=20 > >> > I don't argue anything about this; I want to make it clear the effec= ts > >> > of removing the second "make installworld." > >>=20 > >> No, instead, it needs to use cross-tools or build-tools or some such. = If > >> release uses more things than are available then we may need to have a > >> release-tools concept. Either that or maybe we should actually still = build > >> a > >> full world in the chroot, then for cross builds build another world, b= ut > >> this > >> time a cross-built one. This would probably result in fewer diffs. T= he > >> distribute stuff already uses what is in /usr/obj, so it would just si= mply > >> involve adding an extra buildworld after the world. I would actually = prefer > >> that as it still preserves the "clean room" atmosphere that a release = is > >> supposed to have. > >>=20 > > No, much simpler. :-) > >=20 > > If there are any such tools, we will just need to bootstrap them, i.e., > > build them under chroot and install them before using them. Depending > > on how _old_ your currently running world is this may or may not be > > possible. This is not different from the bootstrap-tools approarch > > in Makefile.inc1. > >=20 > > If your currently running world is nearly the same as the world about > > to be released by "make release", the chances are 100% they will > > bootstrap. This was a prerequisite for the old version, as you may > > have already known. >=20 > If you are going to require this anyways, then why go through all the > extra work to "avoid" it by not doing the installworld of the new native > binaries in the chroot? >=20 > You've now just put back the requirement you were claiming to have elimin= ated. >=20 I'm going to teach release/Makefile how to bootstrap tools that we need during the process. FWIW, I've been able to build 5.0-CURRENT release on a 4.5-STABLE box with some minor changes to release/Makefile that I will commit within an hour. Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8zU7HUkv4P6juNwoRAgIQAJ4nh5/80Cfd8p7096uil0AmvO7HZgCfWj0O zl+TvOlMZaie5fGRkSFe4XQ= =elPT -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4-- 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?20020429134647.GA52838>