On Thu, Nov 26, 2020 at 09:31:30AM +0100, Paul Gevers wrote: > > 1) use 2.0.0+really1.8.3 pattern for our Debian package version > As it seems not unreasonable to expect the upstream version to go past > 2.0.0 in the not infinite future, this is the approach I would take.
well. "not unreasonable" and "not infinite future" could very likely turn into carrying 2.0.0+really1.8.3 for the next 20 years... > > 2) introduce an epoch > Because this you have to carry forever. ...which more or less is the same time span as the above. Also I find 1:1.8.3 not ugly at all, for most use cases this is 1.8.3 so I would go with that. And if someone complains about the 1: epoch one can always point to the upstream issue explaining why this has happened. Oh, and I do find 2.0.0+really1.8.3 and even more 2.0.0+really1.8.4+gitXYZ much more ugly than 1:1.8.3 or 1:1.8.3+gitXYZ -- cheers, Holger ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ holger@(debian|reproducible-builds|layer-acht).org ⢿⡄⠘⠷⠚⠋⠀ PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C ⠈⠳⣄ “If the fires of 2020 horrify you, consider that, no matter what we do, by 2050, when the benefits of even fast climate action will only begin to arrive, the area burned annually in the (US) West is expected to at least double and perhaps quadruple.” (David Wallace-Wells)
signature.asc
Description: PGP signature