From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HpR1A-0001es-6b for garchives@archives.gentoo.org; Sat, 19 May 2007 15:38:52 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l4JFbuvx003651; Sat, 19 May 2007 15:37:56 GMT Received: from mercury.easily.co.uk (mercury.easily.co.uk [212.53.64.51]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l4JFa64S001357 for ; Sat, 19 May 2007 15:36:06 GMT Received: from [81.151.88.253] (account w8ss0jn4va48 HELO c1358217.kevquinn.com) by mercury.easily.co.uk (CommuniGate Pro SMTP 4.0.6) with ESMTP id 218462124 for gentoo-dev@lists.gentoo.org; Sat, 19 May 2007 16:34:10 +0100 Date: Sat, 19 May 2007 17:38:51 +0200 From: "Kevin F. Quinn" To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] distcc and precompiled headers Message-ID: <20070519173851.7c46348f@c1358217.kevquinn.com> In-Reply-To: <47748.192.168.2.155.1179492070.squirrel@www.aei-tech.com> References: <47748.192.168.2.155.1179492070.squirrel@www.aei-tech.com> X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.9; i686-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_K9P+WtwZW5s2Xq5FrL3Q+1K; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Archives-Salt: 70bf4d8e-47cf-4504-b6ec-a61357ec045c X-Archives-Hash: 26db0f7565f9baf889cb96747a7bb173 --Sig_K9P+WtwZW5s2Xq5FrL3Q+1K Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 18 May 2007 08:41:10 -0400 (EDT) "Caleb Tennis" wrote: > Based on some recent findings, it looks like the two above mentioned > features don't work together. pch don't get distributed to distcc > nodes, so they're basically mutually exclusive. However, distcc is a > FEATURE and pch are a USE flag. >=20 > Should we just put a check in each ebuild that uses the pch use flag, > make an eclass, or build something into the package manager(s) ? > Thoughts? I'd go with a 'pch' utility eclass, and have packages that IUSE pch add a call in pkg_setup (which would either die, or disable distcc). On a related note, we had a discussion on bug #128810 a while back about whether the package manager should be doing distcc and ccache at all, anyway. Personally I think the package manager shouldn't be involved in that at all. --=20 Kevin F. Quinn --Sig_K9P+WtwZW5s2Xq5FrL3Q+1K Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTxoL9G2S8dekcG0RAle0AKDAk+YSfrNL1T8hsQRrFLRi//fsQgCfSgR0 /lV3YzYD5KU5VwAJiLDqrbE= =5TFK -----END PGP SIGNATURE----- --Sig_K9P+WtwZW5s2Xq5FrL3Q+1K-- -- gentoo-dev@gentoo.org mailing list