Karl Eichwalder
François Pinard
writes:
| YaST has some code to compare versions, which it uses while upgrading | a distribution from a previous one. I also have, in the Translation | Project, code for comparing versions, but as new packages get poured | int the TP, I keep hitting new versioning schemes. Would SuSE be | kind enough to share with me the experience they gleaned in this area? | That might speed up things on my side, maybe, I'm not sure!
Unfortunately, I'm not at all familiar with YaST sources (C++). AFAIK, we're comparing version numbers and the dates (timestemps of the RPM packages). Maybe, some pathological cases are hardcoded (new version while splitting a package, etc.).
Thanks for your reply, Karl. I revised this area yesterday (to account for CLISP version numbering by ISO dates), and made a Python class to represent versions. I loaded the comparison operators with my own function, which I tried to write cleanly. It does not fundamentally alleviate the problem, but at least, it alleviates the code and makes it more manageable :-). -- François Pinard http://www.iro.umontreal.ca/~pinard -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/