This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Packages that change without incrementing the version/release

Christopher Faylor wrote:
On Sat, Nov 20, 2004 at 03:14:52PM -0000, Max Bowsher wrote:
And one important consequence of this is that packagers must *never* change
files without changing the release number, once they have gone to the
mirrors - because setup.exe will be telling users that something odd has
happened - not just silently ignoring the inconsistency.

I don't agree with this. As you noticed, I recently repackaged some of the xorg stuff to test a theory about why X installs were failing. If I'd bumped the version number then it would have been an indication of a new version of the software -- which was not the case.

In this case, setup.ini correctly represented files available for the
distribution and the files on the users disk were not wrong.  I don't
think that setup should complain about this unless the user specifically
requests a redownload or reinstall.

It may not have been a new version of the software, but it was a new version of the package.

But, philosophical issues aside - how can setup tell the difference between a corrupt package and one that has been 'replaced', and so no longer corresponds to the current info in setup.ini?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]