Date: Mon, 20 Aug 2018 13:04:34 +0930 From: Shane Ambler <FreeBSD@ShaneWare.Biz> To: freebsd-current@freebsd.org Subject: Re: Sharing compiled builds between multiple 12-CURRENT boxes. Message-ID: <b5a1f089-e1e5-6a39-c792-3ffe9320edef@ShaneWare.Biz> In-Reply-To: <2098a6d6-733f-14c4-b4c9-8bc6b3d2fddc@FreeBSD.org> References: <20180818223420.rjisst4vuxzxbcrl@kazhap> <0b28a679-b13c-149b-a7db-12c9f5f41100@ShaneWare.Biz> <2098a6d6-733f-14c4-b4c9-8bc6b3d2fddc@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19/8/18 5:31 pm, Matthew Seaman wrote: > On 19/08/2018 01:55, Shane Ambler wrote: >>> I run 12-CURRENT on few machines, some more powerful that other (all >>> of them x86_64, march varies). > >> You can use freebsd-update by setting up your own update server >> https://www.freebsd.org/doc/en/articles/freebsd-update-server > > freebsd-upgrade(8) only works for releases, and not 12-CURRENT as the OP > specified. While I haven't used it to make releases from current, I would be surprised if it doesn't work for current. The default config for release.sh is to checkout and build HEAD, so without setup, current would be used when building for the update server. I do expect an incremental numbering scheme would need to be used to differentiate each build, patch level builds should fit that. -- FreeBSD - the place to B...Software Developing Shane Ambler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b5a1f089-e1e5-6a39-c792-3ffe9320edef>