I realized when I was looking at bug #34262 that something must be wrong with --nodeps: When emerging distcc before bootstrap, emerge --nodeps distcc should emerge distcc with no dependencies, however, unless the USE flags -gtk and -gnome are set, emerge will fail with configure: error: gtk+-2.0 was not found by pkg-config !!! ERROR: sys-devel/distcc-2.11.1 failed. !!! Function econf, Line 324, Exitcode 1 !!! econf failed Reproducible: Always Steps to Reproduce: 1.On a clean system, stage 1, emerge sync 2.follow the distcc docs exactly: emerge --nodeps distcc before bootstrap 3.emerge should fail as mentioned above Actual Results: emerge failed with: configure: error: gtk+-2.0 was not found by pkg-config !!! ERROR: sys-devel/distcc-2.11.1 failed. !!! Function econf, Line 324, Exitcode 1 !!! econf failed Expected Results: --nodeps should have taken care of USE="-gtk -gnome" and the package should have emerged successfully with no dependencies. If this is not how --nodeps should work, the distcc doc should mention the USE='-gnome -gtk' solution.
I'll have an updated .xml file shortly. FWIW, you should do USE='-*' emerge --nodeps distcc
Docs team : Attached is an updated XML file
Created attachment 21298 [details] new xml file
Lisa: can you provide a diff between your new version and the former one? If not, that's okay, I'll search for the differences manually then (but that'll take a bit longer).
Yeah, go to: http://www.thedoh.com/viewcvs/distcc/html/distcc.xml?r1=1.11&r2=1.12&diff_format=h
Okay, although I'm not really happy with pointing to bugreports in the documentation, I have too little experience to propose anything saner. Committed. Thank you lisa, glad to have a non-doc developer writing documentation, makes it a lot more easy for us :)
I was updating the French translation when I noticed the following: Step 2: Getting Distcc Telling a user he might have to emerge pkgconfig is not very helpful, is it? How does he know beforehand or how does he find out? Fro what I read in the mentioned bug, wouldn't it be clearer to tell a user he should emerge pkgconfig if the emerge distcc fails with 'pkg-config: command not found' and then try again? Future Plans: distcc-config is out of date and has been rewritten. That's quite contradictory isn't it? And why is that mentioned in chapter <Future Plans> ?
See comment above. I shall post a patch soon(ish).
Created attachment 23936 [details, diff] distcc.xml.patch 1- Tried to make note about pkg-config more explicit 2- Note about history of distcc-config has no place in "future plans" section Please review
Patch looks good
Committed.
