1 |
Sascha Lucas wrote: |
2 |
> |
3 |
> Hi List, |
4 |
> |
5 |
> Machine B: |
6 |
> - mount PGKDIR of machine A via nfs to PGKDIR on machine B |
7 |
> - added USE-flag "samba" |
8 |
> - emerge -uD --newuse --usepkg world |
9 |
> * merges binary samba |
10 |
> * does not merge anything else (no binary, no ebuild ) |
11 |
> |
12 |
> It would be nice if I understand why emerge won't remerge binary packages |
13 |
> with changed use-flags. |
14 |
|
15 |
Hi Sascha |
16 |
|
17 |
If you do --pretend --verbose, does it show the changed USE flags for |
18 |
the packages? Not sure if 'world' does this, but you could try the |
19 |
individual packages that you expect to be rebuilt. IIRC, it appears in |
20 |
green (on a colour screen...) with a + and * next to the USE flag. |
21 |
|
22 |
If the flags aren't shown as 'new' then its not strictly a problem with |
23 |
the merge, but one with the way the flag changes are being enumerated. |
24 |
|
25 |
If they are shown as changed then at least Portage is working out that |
26 |
it would like to have new builds of the packages, and any failure is |
27 |
presumably due to the way this cascades down to the binary merge |
28 |
mechanism, such as the ability of a binary package to declare what USE |
29 |
flags it was built with. |
30 |
|
31 |
Not a solution, but hopefully it'll add insight. |
32 |
|
33 |
IanC |
34 |
-- |
35 |
gentoo-user@g.o mailing list |