[[PATCH setup] 0/3] Prepare for colons in version numbers

Brian Inglis Brian.Inglis@SystematicSw.ab.ca
Fri Oct 27 19:48:00 GMT 2017

On 2017-10-27 13:26, Achim Gratz wrote:
> Ken Brown writes:
>> A future version of setup might allow version numbers of the form
>> e:v-r, where is an epoch.  Currently setup doesn't parse these
>> correctly when reading installed.db.  In case ScanFindVisitor is used,
>> there is an additional problem in reading filenames containing colons.
>> The reading is done by Win32 functions, and the illegal characters
>> like ':' aren't translated.
> I don't really think it's worth anybody's while to introduce support for
> a feature (epochs) that everone else decided should not be used.  Do we
> really want to use epochs and what for?

Possibly yes, to avoid users having to manually select upgraded versions, as
when package upstream version numbering changes from say yyyymmdd to v.m.r or
vice versa or something completely different, the higher epoch (original default
is 0:) says this is an upgrade regardless of the rest of the upstream version;
see https://www.debian.org/doc/debian-policy/#version

An alternative could be: upgrade if installed != current, allowing for
downgrades when bugs occur, but presumably this has been discussed before.

Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

More information about the Cygwin-apps mailing list