Hi, Michał Górny wrote: > I see two generic approaches possible here: > > 1. proxying distcc from within the build environment, or > > 2. moving distcc-spawned processes back to parent's namespace. > > > distcc client/server solution > ----------------------------- > > The most obvious solution to me is to employ a client/server model > where a system-wide daemon is running, parsing /etc/distcc/hosts > and doing all the network activity. > > [...]
It is not only distcc. Please don't forget things like sys-devel/icecream. -Thomas
