From owner-freebsd-stable Fri Mar 20 10:32:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21646 for freebsd-stable-outgoing; Fri, 20 Mar 1998 10:32:14 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [207.141.254.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21572 for ; Fri, 20 Mar 1998 10:32:04 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: from shell.futuresouth.com (mail.futuresouth.com [207.141.254.21]) by shell.futuresouth.com (8.8.8/8.8.8) with SMTP id MAA02100; Fri, 20 Mar 1998 12:31:54 -0600 (CST) Date: Fri, 20 Mar 1998 12:31:53 -0600 (CST) From: "Matthew D. Fuller" To: Ted Spradley cc: Drew Derbyshire - UUPC/extended software support , stable@FreeBSD.ORG Subject: Re: after the release ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk On Fri, 20 Mar 1998, Ted Spradley wrote: > > > 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. > > I take exception to the word 'hand' here. You really ought to try to learn a > bit about make and cvs. IMHO, those are two of the most useful things a > computer can do (but they're not graphical, not even interactive, so they're > completely out of fashion (don't *start*, Ted)). And they're not just for > programmers. I'm going to resist the temptation to agree violently with certain sentiments here... > > 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. > > I presume you mean a *binary* patch here. What's the big advantage of > binary over source? You don't have to pay extra for the compiler. I > suppose the binary patch would run faster, but the computer does the > work, not you, so why do you care? The source patch is more likely to > get it right, and if it doesn't, you've got a tiny chance to fix it. Part of the point is so people wouldn't HAVE to have the source to do that patch. If they have the source, and feel comfortable about doing the make world, then they're doing it anyway. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message