Date: Fri, 20 Mar 1998 10:49:44 +0100 From: Eivind Eklund <eivind@yes.no> To: Drew Derbyshire - UUPC/extended software support <software@kew.com>, stable@FreeBSD.ORG Subject: Re: after the release ... Message-ID: <19980320104944.02752@follo.net> In-Reply-To: <3511B113.2EA6CD5D@kew.com>; from Drew Derbyshire - UUPC/extended software support on Thu, Mar 19, 1998 at 06:58:11PM -0500 References: <3511B113.2EA6CD5D@kew.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[Drew Derbyshire] > I would suggest after the release a point release method be > developed to allow (perhaps as a port type package?) The ability to > download/apply critical fixes quickly. > > Simply put, having to track the entire -stable source to get > bugfixes on the CD-ROM is not desirable. Good suggestion! Go ahead and do it; I promise to post comments about your design when you post it, and I'm sure Jordan and Mike will, too. Quick requirements: * Full authorization using public key cryptography * It must be possible to back bad changes out. * It must verify that the base-version it is upgrading from is correct That's about it. You'll get extra points for: * Automatic handling through e-mail * Using the standard metadata format from the Java JAR files for authentication * Being able to apply binary diffs * Writing this so the code can be re-used by the new package system * Getting it done so it can ship with 2.2.6-RELEASE. (This gives LOTS of points, and I'm sure there are several people that'll buy you a beer for this. I'm one of them :-) Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980320104944.02752>