Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 18 Dec 2005 09:55:33 +0000
From:      Matthew Seaman <m.seaman@infracaninophile.co.uk>
To:        Chuck Swiger <cswiger@mac.com>
Cc:        Joe Rhett <jrhett@svcolo.com>, stable@freebsd.org, current <current@freebsd.org>
Subject:   Re: Fast releases demand binary updates.. (Was: Release schedule for	2006)
Message-ID:  <43A53215.8090001@infracaninophile.co.uk>
In-Reply-To: <43A4A557.3010600@mac.com>
References:  <43A266E5.3080103@samsco.org> <20051217220021.GB93998@svcolo.com> <43A4A557.3010600@mac.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig4B2841E627D47D72C34079BE
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Chuck Swiger wrote:
 
> Upgrading the ports from there was somewhat annoying, as this guy's machine had
> ~400 or so, but deleting them all, and then using "pkg_add -r " works just fine
> if you want to grab the latest current binaries.  From there you can portupgrade
> as usual.
> 
> Now, if you want to talk about upgrading to intermediate patch releases, you've
> got a valid point there.  :-)

Doesn't creating a binary updates system that's going to be practical to use
require implementation of that old and exceedingly bikesheddable subject: packaging
up the base system?  After all, you're going to need some mechanism for auditing
servers down the line (yes, this machine has had the vital fix to the foo daemon applied), and while bumping the patch level on the release sorta works to do that,
it implies a new kernel and a reboot for each patch applied if it's going to be
visible.

	Cheers,

	Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.                       7 Priory Courtyard
                                                      Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey         Ramsgate
                                                      Kent, CT11 9PW

--------------enig4B2841E627D47D72C34079BE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDpTIb8Mjk52CukIwRA5ghAJ93xPRSJJcFgNU429W6CRxTSiaf8gCdG93f
DuzOr5UrL/5t59sS6UzD7EM=
=aytM
-----END PGP SIGNATURE-----

--------------enig4B2841E627D47D72C34079BE--



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