Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <00d501c35887$a1df96c0$7d69883e@starfruit>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: "chris" <caj AT cs DOT york DOT ac DOT uk>
Cc: <cygwin AT cygwin DOT com>
References: <bgam88$2pq$1 AT main DOT gmane DOT org> <011401c3575c$904737a0$5400a8c0 AT starfruit> <3F291FEB DOT 7080504 AT cs DOT york DOT ac DOT uk>
Subject: Re: Allowing cygwin setup to patch up old versions
Date: Sat, 2 Aug 2003 00:50:03 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165

chris wrote:
> The patch system I am currently using is my personal conversion of the
> bsdiff package from *BSD. I was intending to submit a cygwinized
> version, but have decided that to be honest the program is not of the
> highest quality, so think a re-write of the program would be useful
> before releasing it on innocent people :)

Just grabbed the package...
Makefile uses syntax not accepted by GNU make.
Uses that <err.h> header which we don't have.
Took a look at the code... Owww! My eyes!

I can see why you backed away from packaging this thing!

> Howev bsdiff does create some
> very small patches, and is specially designed to cope with binaries, and
> the kind of differences you get in binaries, better than normal diff
...
> The other major thing is that what I diff is (obviously) the .tar files,
> not the .tar.bz2 files, as even a small change to a file usually totally
> changes a compressed version of it. The only problem I can see this
> causing is that the bzip2 files must be compressed in exactly the same
> way. However I expect that everyone will compress their .bzip2s with the
> default, and best setting. If it turns out these files drift then I may
> be forced to MD5 the .tar files. I would like to keep the changes
> required as small as possible tho.

It looks like this will work out ok. I've got my machine un-bzip2ing and
re-bzip2ing all the Cygwin packages I have downloaded. It's only got to
P(alphabetically), but that is still a lot of packages. So far, only one
difference: The fortune bz2 has a few KB of nulls appended to the bz2 data,
which of course get stripped by the de/re-compress.

There are only 2 packages left in the distro using gzip-compression (crypt
and irc) - we can probably get those recompressed as bzip2, if it turns out
to be an issue.

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/