This is the mail archive of the
mailing list for the Cygwin project.
Re: [FYI] file conflicts in recent Cygwin packages (see syscheck.log)
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- To: "Stipe Tolj" <tolj at wapme-systems dot de>,<cygwin-apps at sources dot redhat dot com>
- Date: Thu, 15 Nov 2001 07:34:27 +1100
- Subject: Re: [FYI] file conflicts in recent Cygwin packages (see syscheck.log)
- References: <3BF2982D.3D963F7C@wapme-systems.de>
Redirected to cygwin-apps.
----- Original Message -----
From: "Stipe Tolj" <email@example.com>
Subject: [FYI] file conflicts in recent Cygwin packages (see
> I have written a couple of shell and perl scripts that do regression
> and consistency testing on the Cygwin distribution tree and it's
> One of it checks all files included in the tarballs against file
> conflict, i.e. when the same file /usr/local/share/foo is included in
> several packages and has different MD5 hash values or even different
> file sizes.
Thats very useful.
> These file conflicts may indicate problem potentials due to the fact
> that setup.exe doesn't care about previously installed files and
> overwrites them.
This is on my todo list.
> I think these file conflicts should be resolved so the packages are
> consistent. That's why I'm posting this.
> The script also generates SQL import data to pipe to an MySQL
> database. It will be used to reference which files are included in
> which packages and the user may check if the locally installed file is
> corresponding to it.
Hmm, I'm not sure what database we will end up using for local package
mgmt, but I presume this is for script efficiency.
Chris: what would you think of having said MySQL DB on
sources.redhat.com, and new packages get linted against the database?
That should be relatively low intensity...
> BTW, we may include dependance checking using setup.ini and setup.hint
> information for the single packages while file conflicts are detected.
> If you don't mind I will include this to the script.
I'm not sure what you mean here, can you explain further?
> Another script is used to traverse the distribution tree and convert
> all .tar.gz to .tar.bz2 which is obviously the better compression tool
This is wrong. It's up to the package maintainer to choose .tar.gz or
.tar.bz2, and if the package is going to be changed the cygwin version
suffix MUST be bumped.