From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 46F391381F3 for ; Tue, 16 Apr 2013 20:59:47 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A55A5E0AB6; Tue, 16 Apr 2013 20:59:45 +0000 (UTC) Received: from vms173005pub.verizon.net (vms173005pub.verizon.net [206.46.173.5]) by pigeon.gentoo.org (Postfix) with ESMTP id 2D3DAE0AB6 for ; Tue, 16 Apr 2013 20:59:44 +0000 (UTC) Received: from odin.tremily.us ([unknown] [72.68.100.81]) by vms173005.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0MLD005EK8ZJZ720@vms173005.mailsrvcs.net> for gentoo-catalyst@lists.gentoo.org; Tue, 16 Apr 2013 15:59:44 -0500 (CDT) Received: by odin.tremily.us (Postfix, from userid 1000) id 06DFB96D0CB; Tue, 16 Apr 2013 16:59:42 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=tremily.us; s=odin; t=1366145983; bh=lSiiffrFJsRt402C9UPY+mwoIGxicy8OXIWQ6AhDdm0=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=Dc2z+C0vPTfcBfGAgnUzz/wodhoiOfwiQqqqh4DmQoIGe6IaBFk/m26epfajG5xVp nfnImMPBc4SShhu+e4NUI2o3JZR3YinMuR3p4DoXGGfBr78ST7S+UACR+w1Zar5I+u 59/gA/YTJhPwvULEm6+UGui5mjR2Zy3QSdHQLYKQ= Date: Tue, 16 Apr 2013 16:59:42 -0400 From: "W. Trevor King" To: Matt Turner Cc: gentoo-catalyst@lists.gentoo.org, Zac Medico , Brian Dolbec Subject: Re: [gentoo-catalyst] [PATCH 0/2] Blacklisting binary packages Message-id: <20130416205942.GB13055@odin.tremily.us> References: <20130309121023.GE26574@odin.tremily.us> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-catalyst@lists.gentoo.org Reply-to: gentoo-catalyst@lists.gentoo.org MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary=+g7M9IMkV8truYOl Content-disposition: inline In-reply-to: OpenPGP: id=39A2F3FA2AB17E5D8764F388FC29BDCDF15F5BE8; url=http://tremily.us/pubkey.txt User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: 46dc9919-66db-4e25-8836-0f15ca200c24 X-Archives-Hash: 3b58a1e65ca0075f9a0d466add18067c --+g7M9IMkV8truYOl Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 16, 2013 at 01:35:40PM -0700, Matt Turner wrote: > I feel like this is getting out of control. I'm just proposing an alternative approach. Feel free to ignore ;). Also, feel free to tell me to drop this issue for $x weeks until folks have some more free time ;). > There seems to be this overwhelming desire to keep applying hack after > hack to make increasingly obscure -- and fundamentally unsupportable > -- configurations work. I was trying to replace the existing hack (from e7ea409, and 6c0a577 through f6ad38) with a simpler, less obscure one. > Brian mentioned that he talked to Zac and that there was something > that portage should be doing differently about binary packages. Let's > please investigate that a bit further before pursuing other > strategies. I have confidence that if Zac understands and knows about > the problem that he can fix portage. That sounds wonderful. My impression was that neither Portage nor the toolchain ebuilds were going to be changed to address this problem. The last I hear on the Portage front was (quoted in [1]): 10:33 < zmedico> dol-sen: wouldn't it be easier to just migrate those pkgs to EAPI 5 + slot-operator? 10:34 * zmedico doesn't feel like doing extra work when EAPI 5 already does everything we need =E2=80=A6 11:16 < Tommy[D]_> Zero_Chaos: my suggestion: ask the toolchain guys about their preferred way (like updating existing eclass, using a new eclass, moving code into ebuilds) and when you got that, do the needed work, including an EAPI-5 version of toolchain ebuilds If Zac's changed his mind, I'd be happy to wait for the Portage bump that works around poorly specified ABI dependencies. However, note that even some EAPI-5 packages don't use ABI sub-slots to avoid this issue [2], so unless the Portage work-around deals with such ebuilds appropriately, we'll still need some sort of hack in catalyst. Cheers, Trevor [1]: http://mid.gmane.org/20130412162540.GB13054@odin.tremily.us [2]: https://bugs.gentoo.org/show_bug.cgi?id=3D454184#c18 (I'll work up the patches Zero_Chaos asks for in #c19 now, but I expect this is not an isolated event) --=20 This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy --+g7M9IMkV8truYOl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAEBAgAGBQJRbbu+AAoJEEUbTsx0l5OMgI4QAK/d/7slvNQDey+l3Qu+5fug 72iUBEjUzVjuBCJVIRcndpwEYev93lJkouLc0tkk3pyaOjps9ymsk9LF5nCaqF0S n36rPoWSPMQFfHqpOG1cuFtQkPXEairzA+gAWKR4Jqx3U4Ve2/aSScANALp8NtRz AgYRnijq5BUlppFgeSRamxBRqr92RnGIW7OnQaOMgHfQ6JPe7kMsUUHmqYOu1UrA KB+lnCNIauFT9/NgM6AwSmZcgrppfUH9ywY36e5QhOu02AS3YC/8+J2VzHiUc9R4 pKeFaOMKJeS4w6PTYknc2j9m2lULZAomFd9H+8tFFWEb2vto1n3rZPt2blxt/qax MS0+3k3v4RbcLvlGvBX1JH2g/ZFi/SOXMGG5rNASQcQNF1WVhhhgTw/K5Tc/AfZi zwmdRRWizNXzY8TRcQU79Z7cZ9Kt+ydoMGlcQqOHd6mxeX9RA5cRmyED5euW7Oyy 4TT5ug4JFGy1ycM35rpbjCR65bx55rHQPrwIBlFN5cv7trcqDL/hq0NNHXBzmfxa ajDYkpJqUhMH8clNCDIGwQHJYt5IAxK41XCVAHHATJVlsnJZ5BTyA9+Tl15UrGK/ BPza2t5ahKT76F3Z/6iRAOX1uDvERxtRkWTW7FguWAzaFNxkY5YgO2X5KioHomsk StbRxc0nRD7tXxhN/LTt =Uv+6 -----END PGP SIGNATURE----- --+g7M9IMkV8truYOl--