Please consider providing a sub slot (for current net-misc/curl-7.48.0 I would suggest SLOT="0/4.4.0", SONAME version of libcurl.so) which would allow ebuilds which link against libcurl to set a slot operator on net-misc/curl so that an update of net-misc/curl can trigger a rebuild for these applications when necessary.
(In reply to Thomas Deutschmann from comment #0) > Please consider providing a sub slot (for current net-misc/curl-7.48.0 I > would suggest SLOT="0/4.4.0", SONAME version of libcurl.so) which would > allow ebuilds which link against libcurl to set a slot operator on > net-misc/curl so that an update of net-misc/curl can trigger a rebuild for > these applications when necessary. so curl has this funny option: --enable-soname-bump Enable enforced SONAME bump --disable-soname-bump Disable enforced SONAME bump which triggers different behaviour in lib/Makefile which is commented. i'll repeat the comment here but you should read the code for the full story: # Bumping of SONAME conditionally may seem like a weird thing to do, and yeah # it is. The problem is that we try to avoid the bump as hard as possible, but # yet it is still necessary for a few rare situations. The configure script will # attempt to figure out these situations, and it can be forced to consider this # to be such a case! See README.curl_off_t for further details. Currently the ebuild has --disable-soname-bump. So I'm not against adding a subslot, but if I do, then we need to switch to --enable-soname-bump. But following that comment, this should be "necessary for a few rare situations", so my question is, why do we need this in gentoo?
@Thomas, ping. can you give me more context as to why you want this in light of comment #1?
I don't have an actual reason. I filled this request after reviewing multiple ebuilds which are all depending on net-misc/curl. Following the ongoing process of providing/using sub slots I thought net-misc/curl should also provide one to allow emerge to trigger an automatic rebuild when necessary for these packages. However like you have shown net-misc/curl seems to be different and the project claims to do everything they can to prevent breakage of backward compatibility by design. So if you agree we can close this as "Won't fix". Ebuilds depending on net-misc/curl can already depend on net-misc/curl:0= if they want to. If we will ever encounter a breakage we can still decide to set a sub slot which then will trigger a rebuild for those ebuilds which already subscribed to net-misc/curl's not yet explicit set sub slot.
(In reply to Thomas Deutschmann from comment #3) > I don't have an actual reason. I filled this request after reviewing > multiple ebuilds which are all depending on net-misc/curl. > > Following the ongoing process of providing/using sub slots I thought > net-misc/curl should also provide one to allow emerge to trigger an > automatic rebuild when necessary for these packages. > > However like you have shown net-misc/curl seems to be different and the > project claims to do everything they can to prevent breakage of backward > compatibility by design. > > So if you agree we can close this as "Won't fix". Ebuilds depending on > net-misc/curl can already depend on net-misc/curl:0= if they want to. > If we will ever encounter a breakage we can still decide to set a sub slot > which then will trigger a rebuild for those ebuilds which already subscribed > to net-misc/curl's not yet explicit set sub slot. triggering rebuilds is a necessary evil. if we have to in order to avoid breakage, we do. but curl upstream claims we can avoid it, so we will. its resolved upstream, sorta ;)
