From owner-freebsd-stable Fri Mar 20 14:32:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11747 for freebsd-stable-outgoing; Fri, 20 Mar 1998 14:32:00 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11580 for ; Fri, 20 Mar 1998 14:31:14 -0800 (PST) (envelope-from danny@panda.hilink.com.au) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id JAA03499; Sat, 21 Mar 1998 09:30:53 +1100 (EST) Date: Sat, 21 Mar 1998 09:30:52 +1100 (EST) From: "Daniel O'Callaghan" 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 Drew, Ted, On Fri, 20 Mar 1998, Ted Spradley wrote: > 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. > > > > To Not everyone installs sources. Many of my customers have brain seizures if I send them step-by-step instructions on how to apply a patch and type 'make ; make install'. I found it easier to create a pkg and tell them to do pkg_add ftp://ftp.hilink.com.au/pub/FreeBSD/sendmail-security-pkg.tgz (sample URL) They were quite happy with the above. As Mike stated, you just need a before and after system where you can compare binaries, then you tar up the binaries from the 'after' system and put them in a package. This allows people who are afraid of 'make' to upgrade. There should be a bit of discussion about when to release an upgrade package, and whether they should be incremental, or complete from the -RELEASE. My vote is for incremental, and at least a week apart, unless there are security holes found. Monthly would probably be acceptable. So, Drew, the two approaches to take are: * install CVS so you can extract the differences you want (Eivind has nice patches to CVS to allow this). * Regularly fetch a SNAP/BETA snapshot from releng22.freebsd.org:/pub/FreeBSD ; unpack it ; compare it with the last one ; create a directory tree with the changed files ; use pkg_create Your new P166 will be up to this job admirably. I just hope you got a decent HDD :-) If you want a hand with this, I am happy to help. Danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message