| 1 |
On Tue, 04 May 2010 11:00:01 +0200, Helmut Jarausch wrote about |
| 2 |
[gentoo-user] emerge --update - why doesn't it update my kde packages: |
| 3 |
|
| 4 |
[snip] |
| 5 |
>Still, eix confirmed there were quite a lot of kde packages which have |
| 6 |
>newer versions, and indeed, |
| 7 |
>emerge -auv1 -j4 --keep-going $(qlist -IC kde-base/) |
| 8 |
>upgraded 24 packages. |
| 9 |
> |
| 10 |
>Where does this discrepancy come from? |
| 11 |
|
| 12 |
I think Portage does not consider packages that are not in your world |
| 13 |
file, if the update is on world (or system). |
| 14 |
|
| 15 |
To overcome this, I wrote a little script, called update_orphans.sh. |
| 16 |
Here it is: |
| 17 |
|
| 18 |
<-------cut-----------> update_orphans.sh <----------cut-------------> |
| 19 |
#!/bin/sh |
| 20 |
|
| 21 |
eix -u | gawk '/^\[U\] / { print $2; }' | xargs -r emerge -v1uD |
| 22 |
|
| 23 |
exit $? |
| 24 |
<-------cut-----------><--------cut------><----------cut-------------> |
| 25 |
|
| 26 |
I run it immediately after the main emerge, when I have rsync'ed the |
| 27 |
Portage tree. |
| 28 |
-- |
| 29 |
Regards, |
| 30 |
|
| 31 |
Dave [RLU #314465] |
| 32 |
====================================================================== |
| 33 |
dwnoon@××××××××.com (David W Noon) |
| 34 |
====================================================================== |
Archives