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