| 1 |
On 14/07/2016 04:03, James wrote: |
| 2 |
>> It's unsurprising you got different behaviour |
| 3 |
> true, but the -u was in both and a complete different set of |
| 4 |
> packages was considered, by portage, and only one was able to |
| 5 |
> move forward (note the -p was not in the second entry, despite |
| 6 |
> my not including that detail). |
| 7 |
|
| 8 |
without -N or -t, portage considers just the list of packages on the |
| 9 |
command line. |
| 10 |
|
| 11 |
-N is newuse, portage also considers packages whose USE has changed. |
| 12 |
-t is emptytree, portage also considers the entire tree and -u tells it |
| 13 |
to not remerge things that don't need updating. |
| 14 |
|
| 15 |
The input set for those commands differs, so the output set might also |
| 16 |
be different. Those two commands you ran are not guaranteed to produce |
| 17 |
the same results (although the often will). |
| 18 |
|
| 19 |
|
| 20 |
-- |
| 21 |
Alan McKinnon |
| 22 |
alan.mckinnon@×××××.com |
Archives