Dnia 20 września 2017 10:23:42 CEST, "Andreas K. Huettel" <dilfri...@gentoo.org> napisał(a): >Am Dienstag, 19. September 2017, 22:38:17 CEST schrieb Luca Barbato: >> > REQUIRED_USE="^^ ( sunrpc libtirpc ntirpc )" >> > If rpc support is optional with useflag rpc, then this becomes >> > REQUIRED_USE="rpc? ( ^^ ( sunrpc libtirpc ntirpc ) )" >> > >> > Since the three options are coinstallable I see no problems with a >package >> > only supporting a subset, but I have no clue how this interacts at >> > runtime. >> >> If they aren't ABI-compatible you would expect explosions once you >link >> two libraries linked to the two different implementation (assuming >they >> aren't macro-mangling everything). > >Yep. So, apart from requiring "use the same implementation everywhere", >i.e. >set the flag globally, and stating "if you micromanage, you have to >contain >the explosions yourself" - is there anything else we can realistically >do?
dev-libs/foo[sunrpc=,tirpc=...]? > >> We could check if the other libc could be switched to the external >> provider and play the lazy card and just always force an external >> implementation. > >Two or three implementations doesnt make that much of a difference >anymore... -- Best regards, Michał Górny (by phone)
