Makoto MATSUSHITA wrote:
>
> obrien> However, today's buildworld is more resilent having better
> obrien> build-tools, etc.. targets than when release/Makefile was
> obrien> first written. Maybe this need could be removed. But this
> obrien> hasn't happened yet.
>
> If I understand the facts of src/release/Makefile correctly,
>
> - First 'make installworld' under /usr/src is for "creating a chroot
> environment for further release engineering." Maybe it can be
> supercedesed by copying existing environment or just extracting
> 'bin' distribution. But there is no tool for this.
Yes, and just doing a make installworld is the easiest way to do this.
> - Second 'make buildworld' inside a chroot environment is the actual
> build procedure. Obviously, it cannot remove :-)
>
> - Second 'make installworld' inside a chroot environment is for
> "creating an environment for further _actual_ release procedures."
> Even though we have much much better procedures for build-tools,
> _actual_ release procedures (release.[1-9], doc.?, cdrom.?, and
> ftp.? target in src/release/Makefile) does not consider about
> that. If these procedures requires newer version of toolchain, it
> should be a release-breaker.
Well, it is similar to the reason we have build-tools, etc. in the
world. We want to make sure that we have tools that match the release
Makefile we are using. Also, it is a good test, since we need to make
sure that the sources can do an actual installworld before we ship them
out to people. :)
--
John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
