| 1 |
Hello Maxim |
| 2 |
|
| 3 |
On 15:46 Mon 16 Jul, maxim wexler wrote: |
| 4 |
> At tail of emerge --sync its says now emerge portage. |
| 5 |
|
| 6 |
Yes, it does that every time there is a new portage version available. |
| 7 |
|
| 8 |
> emerge -u portage lines up 5 or 6 packages plus |
| 9 |
> portage, 18Mb. |
| 10 |
|
| 11 |
from the emerge manpage: |
| 12 |
|
| 13 |
"--update (-u) |
| 14 |
Updates packages to the best version available, which may not always be the |
| 15 |
highest version number due to masking for testing and development. This will |
| 16 |
also update direct dependencies which may not be what you want. Package atoms |
| 17 |
specified on the command line are greedy, meaning that unspecific atoms may |
| 18 |
match multiple installed versions of slotted packages." |
| 19 |
|
| 20 |
> So why doesn't it list the upgrade part now? |
| 21 |
|
| 22 |
If you look carefully at the first line 'emerge -pv portage' gives you, |
| 23 |
you will notice that it says `[ebuild R ] sys-apps/portage'. The `R' |
| 24 |
is for `Rebuild' - as your portage is already at the latest version |
| 25 |
emerge wants to rebuild it. If you use the -u flag it just searches for |
| 26 |
updates, finds none and hence does not suggest any installation. |
| 27 |
|
| 28 |
I suggest you should read throgh emerge(1) and portage(5) mapages and |
| 29 |
also read the online docs in the handbook to get familiar with the |
| 30 |
portage system. |
| 31 |
|
| 32 |
|
| 33 |
Regards, |
| 34 |
Aleks |
Archives