| 1 |
Am 04.05.2010 16:59, schrieb David W Noon: |
| 2 |
> On Tue, 04 May 2010 11:00:01 +0200, Helmut Jarausch wrote about |
| 3 |
> [gentoo-user] emerge --update - why doesn't it update my kde packages: |
| 4 |
> |
| 5 |
> [snip] |
| 6 |
>> Still, eix confirmed there were quite a lot of kde packages which have |
| 7 |
>> newer versions, and indeed, |
| 8 |
>> emerge -auv1 -j4 --keep-going $(qlist -IC kde-base/) |
| 9 |
>> upgraded 24 packages. |
| 10 |
>> |
| 11 |
>> Where does this discrepancy come from? |
| 12 |
> |
| 13 |
> I think Portage does not consider packages that are not in your world |
| 14 |
> file, if the update is on world (or system). |
| 15 |
> |
| 16 |
> To overcome this, I wrote a little script, called update_orphans.sh. |
| 17 |
> Here it is: |
| 18 |
> |
| 19 |
> <-------cut-----------> update_orphans.sh<----------cut-------------> |
| 20 |
> #!/bin/sh |
| 21 |
> |
| 22 |
> eix -u | gawk '/^\[U\] / { print $2; }' | xargs -r emerge -v1uD |
| 23 |
> |
| 24 |
> exit $? |
| 25 |
> <-------cut-----------><--------cut------><----------cut-------------> |
| 26 |
> |
| 27 |
> I run it immediately after the main emerge, when I have rsync'ed the |
| 28 |
> Portage tree. |
| 29 |
|
| 30 |
No. --with-bdeps is not default anymore because it is considered to be a |
| 31 |
bug if portage updates packages not used in any way. This is only if a |
| 32 |
package is needed for buildtime. |
| 33 |
|
| 34 |
Program A is version 1.5. To build it, it needs program B which at this |
| 35 |
time is version 4.7 |
| 36 |
B is not needed for anything else! |
| 37 |
|
| 38 |
Now there is an update to B-4.9 . Portage will not update B as long as |
| 39 |
there is no update to A. |
| 40 |
|
| 41 |
B is not in the world file. It is not a runtime dependency nore is it a |
| 42 |
orphan. |
| 43 |
|
| 44 |
kh |
Archives