https://bugzilla.redhat.com/show_bug.cgi?id=1490053 --- Comment #4 from Alexander Ploumistos <alex.ploumistos@xxxxxxxxx> --- (In reply to Antonio Trande from comment #3) > What is confused to me are the Provides/Obsoletes lines > > Provides: liborigin = 20080225-18 > Provides: liborigin2 = 2.0.0-12 > Obsoletes: liborigin < 20080225-18 > Obsoletes: liborigin2 < 2.0.0-12 > > In this way, you are replacing liborigin and liborigin2 de facto, so an user > cannot install liborigin/liborigin2 and SciDAVis/liborigin3 in the same time. But that is the point. The older library, liborigin can import OPJ files created with Origin v3.something to v4.something, while liborigin2 works with versions 4.1 to 8.5.1. That is the reason why in most distributions, including Fedora, instead of updating liborigin to v2.0.0, the older library was kept around based on the last v1.x snapshot and a liborigin2 package was introduced. The newer version -let's call it liborigin3 for the time being- can import OPJ files from Origin version 3.5 all the way to current ones (9.4.1 and newer), so its functionality includes and exceeds that of the two others, plus a number of bugs in the older code have been fixed. It also has fewer dependencies. Why would anyone want to have all three of them installed at the same time? I could be wrong, but as far as I know, there is no currently maintained program (both inside and out of Fedora) that requires the old libraries. You maintain a lot of related packages, would you happen to know of one? > In my opinion, providing unofficial 'liborigin3' as private SciDAVis library > it's better, as long as it is officially released. I wouldn't mind doing that, but I find it a bit confusing moving forward from there. * In the spec file, would it be Provides: bundled(liborigin) = 3.0.0.pre or Provides: bundled(liborigin3) = 3.0.0.pre ? * Do I keep both liborigin and liborigin2 around until the official release of v3.0.0? It seems unlikely that a package depending on either of them will pop up in the meantime. * Would there be any problems if instead of introducing a third version of the library, I update liborigin to v3.0.0? That would render this review request moot… It goes without saying that you have a lot more experience than I do and since you disagree with my proposed approach, I would be really grateful if you could lay out a plan for me on how to deal with all four packages - scidavis, liborigin, liborigin2, liborigin3. Best regards -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx
