| 1 |
On Fri, 18 May 2007 08:41:10 -0400 (EDT) |
| 2 |
"Caleb Tennis" <caleb@g.o> wrote: |
| 3 |
|
| 4 |
> Based on some recent findings, it looks like the two above mentioned |
| 5 |
> features don't work together. pch don't get distributed to distcc |
| 6 |
> nodes, so they're basically mutually exclusive. However, distcc is a |
| 7 |
> FEATURE and pch are a USE flag. |
| 8 |
> |
| 9 |
> Should we just put a check in each ebuild that uses the pch use flag, |
| 10 |
> make an eclass, or build something into the package manager(s) ? |
| 11 |
> Thoughts? |
| 12 |
|
| 13 |
I'd go with a 'pch' utility eclass, and have packages that IUSE pch add |
| 14 |
a call in pkg_setup (which would either die, or disable distcc). |
| 15 |
|
| 16 |
On a related note, we had a discussion on bug #128810 a while back about |
| 17 |
whether the package manager should be doing distcc and ccache at all, |
| 18 |
anyway. Personally I think the package manager shouldn't be involved in |
| 19 |
that at all. |
| 20 |
|
| 21 |
-- |
| 22 |
Kevin F. Quinn |
Archives