This is the mail archive of the cygwin-apps 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: [[PATCH setup] 0/3] Prepare for colons in version numbers

Am 30.10.2017 um 16:58 schrieb Jon Turney:
"everyone" != "everyone, ignoring people who disagree with me"

I think this is an unfair summary of my position.

If you think epochs are a bad idea, you need to give reasons, not just pretend there is no debate.

I was strictly talking about those folks who've had the opportunity in practise so far, which is all the major GNU/Linux distributions. The ones I'm aware of aren't using epochs and instead decided to use other means of achieving the same (or similar) goals. In fact they created rules to not use epochs even though the tools support them. Their line of reasoning always was (and still is), that once you start using epochs there is no way going back and you could just as well have used monotonic release numbers instead of versions. The other point is that it is close to impossible that everybody will agree on what the epoch ought to be. The last point is that once an epoch bump is introduced, you can't decide to sort things differently unless you're prepared to invalidate all existing released packages.

So, we might have that debate now for Cygwin because we might finally use a library that supports epochs, but others have been there before us and concluded that epochs aren't worth the trouble. I don't see our situation with Cygwin different enough to come to a different conclusion than the distro folks and they've had many more brains to pick on this issue.

I agree it does not work well for CPAN-style floating point version numbers, but that's your problem to solve, or not, however you like...

You can stop using this particular example if it helps you not taking a right at Albuquerque each time version numbers come up. This is just one of many examples where two sets of sane versioning rules don't produce the same ordering.

There are plenty of other examples where versioning upstream for whatever reason doesn't conform to whatever set of rules to make them sortable and it's not all that unheard of that upstream decides to change their rules once in a while even if they otherwise keep their stride.

So whatever the reason, you will have to impose a sort order whenever there is a package that doesn't follow the rules builtin to setup and hence sorts incorrectly. You say epochs are _the_ way to do that and I'm pointing out that the distro folks have come to the conclusion that it isn't and are using different mechanisms.


(on the road :-)

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