Date: Fri, 20 Mar 1998 08:51:31 -0500 From: Drew Derbyshire - UUPC/extended software support <software@kew.com> To: stable@FreeBSD.ORG Subject: Re: after the release ... Message-ID: <35127463.6ACB464@kew.com> References: <3511B113.2EA6CD5D@kew.com> <19980320104944.02752@follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Eivind Eklund wrote:
> [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.
Drop dead. You can say it's boring to do and that Real Programmers (TM) don't
need it, go ahead, but I don't need the sarcasm.
I neither a CVS expert nor directing FreeBSD release policy. I'm only
pointing out a failure in the FreeBSD release cycle, as Jordan pointed out HP
and Sun have bugs, but THEY have a packaged patch process. FreeBSD does not,
it only has "upgrade to the next release" or hand patch any fixes into the
source and rebuild. Adding such a patch function seems to be an issue of
packaging a limited number of critical changes (in 2.2.5 for example, it would
have been the lpd and the security fixes) into a package. Under System V, it
would be pkgadd. Under FreeBSD the best method seems to be ports.
You can disagree with me, but I don't need to be ridiculed for making a valid
suggestion.
-ahd-
--
Drew Derbyshire UUPC/extended e-mail: software@kew.com
Telephone: 617-279-9812
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?35127463.6ACB464>