1 |
On Saturday 23 February 2008, Erik wrote: |
2 |
|
3 |
> I check with the file klibc-1.5.8.tar.bz2. |
4 |
> # emerge -up klibc |
5 |
> |
6 |
> These are the packages that would be merged, in order: |
7 |
> |
8 |
> Calculating dependencies... done! |
9 |
> [ebuild U ] dev-libs/klibc-1.5.8 [1.5] |
10 |
> |
11 |
> So it seems like klibc is outdated but "emerge -uDNav world" does not |
12 |
> want want to update it! |
13 |
> # equery d klibc |
14 |
> [ Searching for packages depending on klibc... ] |
15 |
> sys-apps/v86d-0.1.3 (dev-libs/klibc) |
16 |
> localhost ~ # grep sys-apps/v86d /var/lib/portage/world |
17 |
> sys-apps/v86d |
18 |
> |
19 |
> So sys-apps/v86d is in world and depends dev-libs/klibc, but yet |
20 |
> "emerge -uDNp world" does not want to update dev-libs/klibc, like |
21 |
> "emerge -up dev-libs/klibc" wants to! |
22 |
|
23 |
|
24 |
This looks like a --bdeps situation. v86D DEPENDS on klibc, it does not |
25 |
RDEPEND on it, meaning that klibc does not need to be updated to |
26 |
*build* a new v86d. |
27 |
|
28 |
v86d is in world so it will be updated because you told portage to |
29 |
always keep it up to date. klibc is not in world and a new updated |
30 |
klibc is not required to accomplish what you have asked to for - a |
31 |
complete update of every package that world expands to with |
32 |
dependencies taken into account. |
33 |
|
34 |
Remember what "world" is - it's a list of packages that you have |
35 |
explicitly asked to be there. It is NOT a list of everything you have |
36 |
installed. I can think of two ways to accomplish what you are asking |
37 |
for |
38 |
|
39 |
- use "--with-bdeps y" or include it in EMERGE_DEFAULT_OPTS |
40 |
- put klibc in world |
41 |
|
42 |
-- |
43 |
Alan McKinnon |
44 |
alan dot mckinnon at gmail dot com |
45 |
|
46 |
-- |
47 |
gentoo-user@l.g.o mailing list |