Date: Thu, 15 May 2003 14:10:18 -0700 (PDT) From: Ruslan Ermilov <ru@freebsd.org> To: freebsd-bugs@FreeBSD.org Subject: Re: misc/52122: make release does not use proper binar Message-ID: <200305152110.h4FLAInh021619@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/52122; it has been noted by GNATS.
From: Ruslan Ermilov <ru@freebsd.org>
To: "David O'Brien" <obrien@freebsd.org>
Cc: John Hay <jhay@icomtek.csir.co.za>, bug-followup@freebsd.org
Subject: Re: misc/52122: make release does not use proper binar
Date: Fri, 16 May 2003 00:01:06 +0300
On Thu, May 15, 2003 at 11:31:40AM -0700, David O'Brien wrote:
> On Thu, May 15, 2003 at 08:13:50PM +0200, John Hay wrote:
> > On Thu, May 15, 2003 at 09:58:44AM -0700, David O'Brien wrote:
> > > On Thu, May 15, 2003 at 06:31:42PM +0200, John Hay wrote:
> > > > One reason why it isn't that useful inside the chroot area, is that
> > > > if your running kernel and the newly built bits gets too much out of
> > > > sync you will need to update the machine in any case, so you will
> > > > end up with "new" binaries and a kernel on the machine and so it
> > > > is a "waste" to recompile world inside the chroot area.
> > >
> > > In this case the release died near the end (release.9 target). It was
> > > easy to update the running kernel and reboot. Now we wanted to restart
> > > the release w/o starting from scratch. This release build included ports
> > > README's and Docs, and thus takes a very long time to build. To not have
> > > to start from scratch, I did "chroot ${CHROOT} /bin/sh" and then ran "rm
> > > /tmp/.world_done ; /mk" which should have restarted the release build and
> > > done the mimimum work to finish the release. It didn't because of the
> > > cross-release commit that removed the installworld w/in the ${CHROOT}.
> > > This bit not only me, but another person also building an Alpha snapshot.
> >
> > Maybe the issue is more of documentation? I know hindsight makes it easy,
> > but an installworld inside the chroot area or "world DESTDIR=/chrootarea"
> > should have been enough to get the binaries updated.
>
> It is, and was. The problem is restarting with /mk used to do this for
> you. It stopped and the only documentation was hidding in the commit
> log.
>
It used to, but only "if [ ! -f /tmp/.world_done ]", and you were
way beyond that point, was it release.9? Nevertheless, I'm not
going to repeat all arguments explaining why "make world" in
CHROOTDIR is an etremely bad idea.
In older days, it was necessary to ALWAYS upgrade to a recent
before attempting to "make release". These requirements are
now lifted, and it's often that you can build a fresh snap on
an older system.
Cheers,
--
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305152110.h4FLAInh021619>