Depends on 7395 (go ahead and mark it spanky ;-)) I'm askin for the inclusion of distcc/distccd on the boot image. I'm bootstrapping and emerging with distcc, and everything seems to work fine. As far as issues with distcc/ccache, only one i've seen is libtool one could make a wrapper like colorgcc to get around the symlinking issue, tell what to call based on the argv and features variable... just my two cents
the distcc bootstrap fails on gettext, i'll work on getting that up and running...
Why is it required to be in the build image ? This is the same type of issue as ccache in the build image. I say whoever is going to use these, know what they are doing, and will know to merge them before starting bootstrap. The only real bug will be if say its not possible to merge them *before* starting bootstrap. my 2 cents ..
I was thinking that since distcc is in FEATURES maybe look at a way to get portage to lookup in a file similar to package.mask where packages that fail with distcc can be added so that portage knowns not to use distcc with those. that way a "emerge system" and subsequint "emerge anything" will use distcc unless the package is listed in distcc.mask. that way distcc can become transparent to users in selecting what packages can be compiled suing distcc and which not. The biggest problem with using distcc for myself right now is having to babysit the emerge -u system or emerge - u world incase there is a failed package, manually emerge it without distcc support then emerge -u again as per normal untill another compile fails due to distcc usage.
Here at Hartman Technica we have a network currently with one very fast Gentoo system. We are working to bring all our systems to Gentoo, but some computers are very markedly slower. We would really appreciate being able to get distcc at the very start, before you actually bootstrap, because it would make it very much faster. Just our vote.
distcc would be very nice to have on the LiveCD. If you try to emerge distcc prior to running the boostrap from stage1, it tries to emerge around 37-40 packages with distcc the last one. I have run manually a build on a 400Mhz PII with distcc farm of 8 P4 2.4Ghz machines, MAKEOPTS set to -j16 and it was lightening fast.
See Bug 26414. What needs to happen for this bug to be closed is for distcc to be: 1) Compile a (static) basic distcc (i386) and put it into a tarball with everything set (think --buildpkg). Do not do the symlinking in the tarball 2) Write a bash script to extract the distcc binary and distcc-config script, install it into the chroot, set symlinks and $PATH. 3) Instruct the user to run a configure script to add the distcc user and to install hosts. That should be all that is needed.
See this thread, guys: http://forums.gentoo.org/viewtopic.php?t=75648
*** Bug 18821 has been marked as a duplicate of this bug. ***
I think its safe to declare this bug dead since steps are present in: http://www.gentoo.org/doc/en/distcc.xml to use distcc to bootstrap. These steps are well tested and they work.
