https://bugzilla.redhat.com/show_bug.cgi?id=1111691
--- Comment #11 from David Nichols <da...@qore.org> --- (In reply to Michael Schwendt from comment #7) > Odd. And rather limited. You could not do "Requires: qore-module-api >= > 0.10", for example. Why not > > Provides: qore-module(api) = 0.5 > Provides: qore-module(api) = 0.6 > Provides: qore-module(api) = 0.7 > ... > > and so on? Also I have to say that this would have just a cosmetic benefit. Module APIs (in reality they are ABIs) are not necessarily backwards-compatible. Each module will always only declare one Requires: line for the particular ABI it needs. It's libqore that will declare all the ABIs it supports with the Provides: declarations that allow the RPM system to manage the dependencies properly. Therefore something like: Requires: qore-module-api >= 0.10 would not be used anyway, since 0.11 or higher may not be compatible with 0.10. What the RPM system needs is to know that ABI 0.10 is supported by libqore, which is provided by the Provides: line (now Provides: qore-module-api-0.10). So this is a much better explanation of why I'm using unversioned artificial dependencies. I had gone through this so many years ago that I had forgotten the reasoning behind it until I thought it through again now. thanks, David -- 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@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/package-review
