| 1 |
Hi, |
| 2 |
|
| 3 |
Michał Górny wrote: |
| 4 |
> I see two generic approaches possible here: |
| 5 |
> |
| 6 |
> 1. proxying distcc from within the build environment, or |
| 7 |
> |
| 8 |
> 2. moving distcc-spawned processes back to parent's namespace. |
| 9 |
> |
| 10 |
> |
| 11 |
> distcc client/server solution |
| 12 |
> ----------------------------- |
| 13 |
> |
| 14 |
> The most obvious solution to me is to employ a client/server model |
| 15 |
> where a system-wide daemon is running, parsing /etc/distcc/hosts |
| 16 |
> and doing all the network activity. |
| 17 |
> |
| 18 |
> [...] |
| 19 |
|
| 20 |
It is not only distcc. Please don't forget things like sys-devel/icecream. |
| 21 |
|
| 22 |
|
| 23 |
-Thomas |
Archives