Date: Mon, 20 Oct 2003 10:48:20 +0300 From: Peter Pentchev <roam@ringlet.net> To: Colin Percival <colin.percival@wadham.ox.ac.uk> Cc: freebsd-hackers@freebsd.org Subject: Re: rsync vs installworld Message-ID: <20031020074820.GF57130@straylight.oblivion.bg> In-Reply-To: <5.0.2.1.1.20031020073640.031bf968@popserver.sfu.ca> References: <20031019101653.A29979@tikitechnologies.com> <20031019190036.3426D16A4D7@hub.freebsd.org> <20031019101653.A29979@tikitechnologies.com> <5.0.2.1.1.20031020073640.031bf968@popserver.sfu.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
--sXc4Kmr5FA7axrvy Content-Type: text/plain; charset=windows-1251 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 20, 2003 at 07:41:51AM +0100, Colin Percival wrote: > At 09:19 20/10/2003 +0300, Peter Pentchev wrote: > >On Sun, Oct 19, 2003 at 10:16:54AM -1000, Clifton Royston wrote: > >> In our case we have already built a simple framework for > >> distributing FreeBSD binary packages built within the ports system > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > >> (rsync presently, > >> but extensible to http/https.) I have been hoping that it's possible to > >> build on the "make release" approach to generate a set of binary > >> packages for updates to the base system, distribute those via rsync, > >> and then install the package collection. > > > >Errr, isn't this pretty much what Colin Percival's > >security/freebsd-update port already does? :) >=20 > FreeBSD Update doesn't handle the ports tree. That said, as long as on= e=20 > wishes to track the release branch of base, there's no reason not to use= =20 > FreeBSD Update + portupgrade. > This wasn't an option for the original poster (imp@) because he wanted= =20 > to track -stable. Guess I should've expanded a bit on my ideas here :) What I meant was not that they should use your excellent service as it is, but that they might try to duplicate its functionality - use your tools, the binary diff and the update script, to produce their own update sets for the base system. For the ports tree, well, there is already ports/sysutils/portupgrade which, combined with a reasonably recent INDEX rebuild and a central package repository for packages built using either the package-recursive target or scripts similar to those in ports/Tools/scripts/pkg-stash/, should be a good way to manage package deployment across multiple hosts. G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@sbnd.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 because I didn't think of a good beginning of it. --sXc4Kmr5FA7axrvy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/k5NE7Ri2jRYZRVMRArgUAJ46ZSExoboAxoq+wNCXyUZ6wS0pkQCdEqb9 YgWAnRL340rTvOj7bnCoALk= =DNk5 -----END PGP SIGNATURE----- --sXc4Kmr5FA7axrvy--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031020074820.GF57130>