Re: [gentoo-dev] distcc and precompiled headers
On Fri, 18 May 2007 08:41:10 -0400 (EDT) "Caleb Tennis" <[EMAIL PROTECTED]> 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. > > 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. -- Kevin F. Quinn signature.asc Description: PGP signature
Re: [gentoo-dev] distcc and precompiled headers
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. > > 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? Enhance distcc? lu -- Luca Barbato Gentoo/linux Gentoo/PPC http://dev.gentoo.org/~lu_zero -- [EMAIL PROTECTED] mailing list
[gentoo-dev] distcc and precompiled headers
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. 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? Caleb -- [EMAIL PROTECTED] mailing list
