-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 09/08/13 12:09 PM, Michał Górny wrote: > Dnia 2013-08-09, o godz. 11:48:07 Ian Stakenvicius <a...@gentoo.org> > napisał(a): > >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 > >> On 09/08/13 11:43 AM, Michał Górny wrote: >>> Dnia 2013-08-09, o godz. 17:32:56 Thomas Sachau >>> <to...@gentoo.org> napisał(a): >>> >>>> As the topic says, when someone converts an ebuild to >>>> multilib, please dont disable binary building for other ABIs, >>>> as has already been done for some packages. >>>> >>>> This will break e.g. for users who target 64bit toolchain >>>> and 32bit userland, since those would not get any binaries >>>> from building for none-default ABIs. >>> >>> Then it is a bug that needs to be reported and fixed properly. >>> And you should report it properly, to the proper people rather >>> than stating authoritatively that a silly work-around is a >>> proper solution. >>> > >> I don't think there was anything authoritative about Tommy's >> post? 'Please' is generally a request, isn't it? > > It is a request given by a person not involved with the multilib > work and a request that is exactly the opposite of what we're > doing and recommending so far. Plus it's against QA. > >> I asked Tommy to post this, because I had the impression that >> this method (only building libs for non-native_abi) is the >> perfectly acceptable and proper way to move forward with >> multilib-build.eclass conversion -- and I figured other dev's >> might too, as more and more get involved with converting their >> lib-providing ebuilds to multilib-build et. al.. > > And it is the best method. We're not going to regress into > multilib-portage. > >
...so, allowing for the ability of 32bit userland with 64bit toolchain (via, say, setting ABI_X86=32 in make.conf) using the eclasses is just outright not ever going to happen? Never mind not supporting it, but essentially not allowing it? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iF4EAREIAAYFAlIFHZEACgkQ2ugaI38ACPA0ggEAhTBHdr0H9N6vkbWzpkQOKbF9 yrKGlCsryxs41nQnPfoBAJe4QXtr9cqjaT9C7EO/lYkX1m49uhNdyg2yzhe1iDlq =I4UD -----END PGP SIGNATURE-----
