Date: Sat, 20 Aug 2005 13:52:36 -0700 From: Colin Percival <cperciva@freebsd.org> To: John Baldwin <jhb@FreeBSD.org> Cc: cvs-src@FreeBSD.org, Doug Barton <dougb@FreeBSD.org>, cvs-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: cvs commit: src/sys/conf newvers.sh Message-ID: <43079814.8030107@freebsd.org> In-Reply-To: <200508201437.36296.jhb@FreeBSD.org> References: <200508190356.j7J3uj5D095435@repoman.freebsd.org> <43059925.3090701@FreeBSD.org> <4305FD75.80501@freebsd.org> <200508201437.36296.jhb@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
John Baldwin wrote:
> On Friday 19 August 2005 11:40 am, Colin Percival wrote:
>>When running
>>FreeBSD Update builds, I'll typically have a RELEASE-pX tree checked out
>>and a security patch (which is going to get committed to the tree later);
>>I want to be able to build tree + patch with a label of RELEASE-p{X + 1}.
>
> If you used 'make release' to build your custom release (like a lot of other
> folks do) you would have had all this for free. :)
I'm not building a release; I'm building and installing a new world and
kernel. For FreeBSD Update, I need the actual files which people will have
installed on their systems, not the ISO images and FTP install tree.
Colin Percival
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43079814.8030107>