On Friday, 11 March 2005, at 20:11:43 (+1300), Darryl Dixon wrote: > Aha! Now I understand. So your primary objection to epoch is that > it overrides sane versioning practises Exactly. It allows a package of an inferior version to upgrade (read: replace) a package of a superior version and to allow a package of an inferior version to prevent updating to a superior version. > So what about when across a program's lifetime it doesn't follow > this utopia? This situation requires some manipulation, yes. But only once. After the old-scheme package is replaced with the new-scheme package, the problem is solved. There is no need for continuing to drag along the solution to this (temporary!) problem in perpetuity. > Concrete examples of how to do this with RPM, please? Have you seen the source code to anaconda lately? I assure you, no one will notice One More Hack(tm). :-) You can also do some tricks with Obsoletes or maintain a list of conversions, such as "(5.0, 5.00503) -> 5.5". Pretty much anything that is independent of the package itself and/or does not require eternal life is better than Epoch. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ <mej@xxxxxxxxx> n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "Love tried to find you. So many times it was just one step behind you. So turn around. What have we got to lose? Let's take tonight before it's over. I'll open my heart for you; just let your love go free." -- Bernard Oattes, "Throw Your Fears to the Wind" _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
