https://bugzilla.redhat.com/show_bug.cgi?id=1359412 --- Comment #18 from Andrew Schorr <ajschorr@xxxxxxxxxxxxxxxxxxxx> --- Hi David, Just as I thought we were all set to go, I realized that there is a subtle versioning issue here. We are soon going to release gawk version 4.2, and that versions bumps the major API version from 1 to 2. When the major API version changes, that signals an incompatibility with previous versions. If gawk 4.2 tries to load a gawk-xml extension that was compiled in a gawk 4.1 build environment, the program will issue an error message about the version mismatch, and then it will exit. I'm not quite sure how to address this. The current gawk-xml 1.0.6 version I just realized should build successfully against both the current gawk 4.1 releases and the new 4.2 release coming soon. But if it's built against 4.1 and then gawk is upgraded to 4.2, it will stop working. It doesn't seem as if the standard "Requires:" and "BuildRequires:" tags capture the subtlety of this situation. It's not quite accurate to say "Requires: gawk = 4.1", since this package could be built against 4.2. But lacking a better solution, is it safest to change the Requires tags to say "gawk = 4.1"? Or is there a better way to address this situation? I suppose we might want to patch the gawk.spec file to add "Provides:" tags for the gawk major and minor API versions: Provides: gawk-api-major = 1 Provides: gawk-api-minor = 1 But is there then some way to specify that the gawk extension libraries will require versions calculated at build time? In any case, I think it's probably a good idea to add the gawk-api versions to the gawk spec, since gawk versions may change more quickly than API versions. Thanks, Andy -- 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
