https://bugzilla.redhat.com/show_bug.cgi?id=1359412 --- Comment #19 from David Kaspar [Dee'Kej] <dkaspar@xxxxxxxxxx> --- Hello Andy, first to start - we need to take into account that rpmbuild is actually quite clever regarding the automatic detection of library requirements. If the gawk-xml will be build against gawk-4.1, it will require at least the gawk-4.1 version. (Taken that gawk is correctly versioning its shared libraries...) In other words, if we make sure the correct version of gawk will be used during build of gawk-xml, we should be at least ok regarding the ABI compatibility. That can be achieved by using the Requires and/or BuildRequires correctly. Regarding the API compatibility... AFAIK, we don't have any gawk-api-major package/binary file, right? I'm not sure that > Provides: gawk-api-major = 1 > Provides: gawk-api-minor = 1 would work. I will discuss it with my colleague. My suggested approach to this (if I understood the problem correctly) would be this: 1) Wait for gawk-4.2 release, rebase it in Rawhide and see if it would be possible to get it into F27 as well. 2) Make necessary changes in gawk-xml and gawkextlib specfiles as needed, for Rawhide (and F27 if needed). 3) Make sure we release the gawk-xml and gawkextlib after the gawk-4.2 lands in Rawhide (and F27 possibly). The necessary changes in 2) that should be enough (IMHO): * In gawkextlib: Requires: gawk >= 4.2.0 # The exact version will be confirmed later IIRC, the gawkextlib is required by any extensions for gawk. And because the gawkextlib will be build against correct gawk version, therefore the extension (like gawk-xml) should also be using correct version of gawk (because the dependency in this case is transitive). Do you agree that this should be enough, or did I miss some important point that will needs to be addressed as well? :) -- Dee'Kej -- -- 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
