1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On Sunday 16 May 2004 00:43, Andrew Gaffney wrote: |
5 |
> Marius Mauch wrote: |
6 |
> > On 05/14/04 Andrew Gaffney wrote: |
7 |
> >>In my digging for how Portage really works, I've come across yet |
8 |
> >>another oddity. In 'emerge -ep xfree', I get: |
9 |
> >> |
10 |
> >>[ebuild N ] sys-devel/bc-1.06-r5 |
11 |
> >> |
12 |
> >>but 'qpkg -q -nc -I bc' shows: |
13 |
> >> |
14 |
> >>sys-libs/glibc-2.3.3_pre20040420 |
15 |
> >>DEPENDED ON BY: |
16 |
> >> elfutils-0.94-r1 |
17 |
> >> prelink-20040317 |
18 |
> >>sys-devel/bc-1.06-r5 <--------- |
19 |
> >>DEPENDED ON BY: <--------- |
20 |
> >> SYSTEM PROFILE <--------- |
21 |
> >>dev-libs/libcroco-0.5.1 |
22 |
> >>DEPENDED ON BY: |
23 |
> >> librsvg-2.6.4 |
24 |
> >>dev-libs/libcdio-0.66 |
25 |
> >>DEPENDED ON BY: |
26 |
> >> vcdimager-0.7.20 |
27 |
> >> |
28 |
> >>If bc is only in the system profile and not depended on by anything |
29 |
> >>else, why is it getting dragged in by xfree? |
30 |
> > |
31 |
> > Because portage checks the system profile everytime, not just for |
32 |
> > `emerge system`. |
33 |
> |
34 |
> Then why doesn't the *entire* system profile get included? |
35 |
|
36 |
Something wrong with qpkg it seems... it probably doesn't check further if |
37 |
it's a system package. |
38 |
|
39 |
bc < openssl < perl < xfree |
40 |
|
41 |
Regards, |
42 |
Jason Stubbs |
43 |
-----BEGIN PGP SIGNATURE----- |
44 |
Version: GnuPG v1.2.4 (GNU/Linux) |
45 |
|
46 |
iQCVAwUBQKZKPloikN4/5jfsAQLPHwP/aWy+h4i+j5kd0OLdBEns1RVINyeE8Bf2 |
47 |
ejerUWHZZq66oVgjw8U3yRll3PI6zZ3M2RrhhhzhxOpOHvnIGWqGsf6FFsL7OUz4 |
48 |
yL6ABErtsSgjziBUDt8lUPFCgc8lTDhth84ZAuKGiOMocpxwMSwHGyPA74Yo2M4B |
49 |
bUgjF2pgRaU= |
50 |
=QVJZ |
51 |
-----END PGP SIGNATURE----- |
52 |
|
53 |
-- |
54 |
gentoo-dev@g.o mailing list |