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? :) > > FreeBSD Update doesn't handle the ports tree. That said, as long as one > wishes to track the release branch of base, there's no reason not to use > FreeBSD Update + portupgrade. > This wasn't an option for the original poster (imp@) because he wanted > 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 -- Peter Pentchev [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] 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.
pgp00000.pgp
Description: PGP signature
