Am 28.09.2013 00:22, schrieb Alan McKinnon: > This only works right if the ebuild maintainer is on the ball, watches > Changelogs for the DEPENDS packages and put the proper metadata in the > ebuild. You can imagine how this can work out very very well when done > right, and if the maintainer makes a mistake (or doesn't clearly > understand how it works) it can cause many unneccessary rebuilds (but > not actually *break* stuff). Huge packages like LO with many > interconnected DEPENDS are always going to be the usual victim I'm afraid... > > And then there's things that use poppler, boost, PyQT and pykde4 - a > similar effect is at work. > > End result = your cpus will be kept nice and toasty warm doing lots of > compiles but actual breakage of the sort that led to revdep-rebuild > being developed should reduce dramatically. Some unneccessary rebuilds > are the price we pay for not having breakage. > > In Helmut's specific case here, the cause seems to be python-exec. I > missed that one myself somehow so had no idea it was hanging around > biting folks.
For the last few days my desktop machine always wants to rebuild tons of stuff like LibreOffice and PyQt4 etc ... And it doesn't get to an end ... right now I say "emerge -1 gcc" and it starts to emerge 13 packages ... with LO rebuilt several times afaik. What to do about this situation? Thanks, Stefan
