From owner-freebsd-hackers Thu Mar 27 00:38:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA13347 for hackers-outgoing; Thu, 27 Mar 1997 00:38:02 -0800 (PST) Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA13325 for ; Thu, 27 Mar 1997 00:37:57 -0800 (PST) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.7.3) id TAA00373; Thu, 27 Mar 1997 19:52:43 +1100 (EST) Date: Thu, 27 Mar 1997 19:52:42 +1100 (EST) From: "Daniel O'Callaghan" To: Reinier Bezuidenhout cc: dennis , hackers@FreeBSD.ORG Subject: Re: 2.2.1-RELEASE In-Reply-To: <199703270802.KAA02458@oskar.nanoteq.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 27 Mar 1997, Reinier Bezuidenhout wrote: > > You guys ever think of doing a patch release (like a single tarball with > > the changes) for those of us that spent 2 days setting up 2.2R? > > Well .. if anyone is thinking about doing this, I have written a > perl script for one of our productis for doing a Secure field upgrade, > basically the script uses FreeBSD's fetch program with either a web > URL or FTP URL to download a tar/tar.pgp file and automatically > extract and applying an upgrade to the system. I have some more details > on how this mechanism works if anyone is "thinking" about such > a process. I've already spoken with Jordan and others about organising a binary patch package repository for use with pkg_add. I just need to put in the extra effort to track the needed changes to the appropriate releases and organise the packages to be built and distributed. Finding time is hard right now. Perhaps over the Easter break I'll look at it again. Danny