Date: Mon, 01 Jun 1998 12:07:14 -0700 From: Mike Smith <mike@smith.net.au> To: Andrzej Bialecki <abial@nask.pl> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Binary diffs between -RELEASE and -STABLE Message-ID: <199806011907.MAA00849@dingo.cdrom.com> In-Reply-To: Your message of "Mon, 01 Jun 1998 13:11:37 %2B0200." <Pine.NEB.3.95.980601130628.18835A-100000@korin.warman.org.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hi, > > I'm preparing a CD release of 2.2.6 for one of Polish computer magazines. > As someone pointed to me, perhaps it would be better to use -stable for > this (as there were some bugs dicovered in the menatime). However, it > seems wasteful to download the whole distribution (which I'm doing at the > moment - I don't have enough resources to generate release myself) when I > could download only a set of binary patches between 2.2.6-RELEASE and > given 2.2-xxxxxx-SNAP... You can't do this because each entire dist is a single LZW-encoded stream. Changing a single byte in the stream changes everything from there on down. I have a mostly complete tool for producing binary upgrades between one dist and the next, but this is only applicable to installed systems. If you have the resources to build a CDROM image, you have the resources to build a release, as a general rule. Failing that, you could grab the most recent -SNAP off releng22.freebsd.org (it's stale because building -stable on -current is broken at the moment). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806011907.MAA00849>