Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 1 Nov 2004 18:26:07 +0800
From:      Xin LI <delphij@frontfree.net>
To:        Michael Dexter <dexter@ambidexter.com>
Cc:        FreeBSD-qa@freebsd.org
Subject:   Re: Please publish 5.3's 'make release' commands
Message-ID:  <20041101102607.GA2999@frontfree.net>
In-Reply-To: <a0611040abdab9d61911a@[10.0.2.2]>
References:  <a0611040abdab9d61911a@[10.0.2.2]>

next in thread | previous in thread | raw e-mail | index | archive | help

--envbJBWh7q8WU6mo
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Nov 01, 2004 at 10:08:40AM +0200, Michael Dexter wrote:
> Dear release team,
>=20
> Is there any official location of each release's actual 'make=20
> release' commands?
>=20
> 'man release' shows the "sequence of commands ... to build the 4.5=20
> release" which is useful but dated.
>=20
> If such information exists for each release, please direct me to it.
>=20
> If it doesn't exist, I suggest you consider it, perhaps by simply=20
> updating each release's 'release' man page to reflect the commands=20
> used to produce that release.

(Unofficial answer :-)

I think it would be quite straightforward for anyone to construct the
``official'' one theirselves.  It's quite similiar, as you can build
your own 5.3-RELEASE any time you want (after the release engineering
team finally released it, of course):

make release CHROOTDIR=3D/local3/release \
       BUILDNAME=3D5.3-RELEASE \
       CVSROOT=3D/host/cvs/usr/home/ncvs \
       RELEASETAG=3DRELENG_5_3_0_RELEASE

This assumes that you have a empty directory /local3/release, and a
CVS mirror repository stored in /host/cvs/usr/home/ncvs.

With the ability of building a custom release, it's possible to build
your own release which are more compact, or suitable for large scale
deployment (like what I am doing at my company).  Additionally this
gives you an opportunity of carrying your own packages/patches that
is not yet MFC'ed (for some reasons, and we definatelly wants to know
what and why you need so you won't need to make these patches everytime),
etc.

Cheers,
--=20
Xin LI <delphij frontfree net>	http://www.delphij.net/
See complete headers for GPG key and other information.


--envbJBWh7q8WU6mo
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD4DBQFBhg8//cVsHxFZiIoRAi8TAJ9wQQn/PtIbq0t0VMiEDKXncnZS3ACYvXMx
+21k75qQdXpc42TPizHF6Q==
=Y7kf
-----END PGP SIGNATURE-----

--envbJBWh7q8WU6mo--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041101102607.GA2999>