[snip]
Aha! Now I understand. So your primary objection to epoch is that it overrides sane versioning practises that divide a program'sThis is not even close to a fair comparison. Versions are defined by the package, and in no way can a particular release number cause a lower version to be preferred over a higher one. Only an epoch can cause such a fiasco.
lifetime neatly into major version releases (with minor point-releases in between times). So what about when across a program's
lifetime it doesn't follow this utopia? (ie, moving from date-based versioning to Major-Minor-Release versioning) It's all very easy
to say 'well, the programmers are just stupid.' but that seems a little like a cop-out to me. Which leads me
neatly on to:
[snip]
Concrete examples of how to do this with RPM, please?This belief shows a distinct lack of forward thinking. There are other ways to provide smooth transition that do not require maintenance for the entire lifespan of that package. Michael
|
-- Darryl Dixon <esrever_otua@xxxxxxxxxxxxxxxxxxxxxxxxxx> |
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
