On Tuesday 13 April 2010 16:49:44 Helmut Jarausch wrote: > On 13 Apr, Peter Humphrey wrote: > > On Monday 12 April 2010 16:55:38 Paul Hartman wrote: > >> I've been using portage unmasked for a very long time and don't > >> remember having any portage-related problems. I'm sure there must be > >> some (or else why is it still RC?) but for me the new features are > >> worth the potential risk of using less-tested code. > > > > There was a problem with its preserved-rebuild feature for a while; > > several people reported here that they were running it and being told > > they still needed to run it again. > > > > As far as I know, that's the only thing preventing release of v2, and I > > think it's been fixed anyway. > > No, I don't think so. > Just recently, I had to unmerge then emerge wxpython since > emerge @preserved-rebuild > couldn't solve it itself. > > One more "buglet". > When doing emerge -j <no of simultaneous processes> > - which is a very useful feature on a multicore machine - > sometime a package just stops to build (which is reported > as failing package). > Just emerge it again. > So, I'd say some new features are not ready, yet, but still > very useful as they are. > Helmut.
Those sound like ebuild and build system bugs, not something with portage itself. Especially the -j bug - sounds like a race condition caused by a pathetic Makefile -- alan dot mckinnon at gmail dot com
