1 |
On Tuesday 17 July 2007 00:46:08 maxim wexler wrote: |
2 |
> So, emerge portage results in one package being |
3 |
> installed, portage, 61kb. |
4 |
> |
5 |
> emerge -u portage lines up 5 or 6 packages plus |
6 |
> portage, 18Mb. |
7 |
> |
8 |
> Went ahead and just did the one package, figuring |
9 |
> later I could do an emerge -u for the rest of it. |
10 |
> |
11 |
> But this is what happens: |
12 |
> |
13 |
> heathen@localhost ~ $ emerge -pv portage |
14 |
> |
15 |
> These are the packages that would be merged, in order: |
16 |
> |
17 |
> Calculating dependencies... done! |
18 |
> [ebuild R ] sys-apps/portage-2.1.2.9 USE="-build |
19 |
> -doc -epydoc (-selinux)" LINGUAS="-pl" 0 kB |
20 |
> |
21 |
> Total: 1 package (1 reinstall), Size of downloads: 0 |
22 |
> kB |
23 |
> |
24 |
> What I expected. |
25 |
> |
26 |
> heathen@localhost ~ $ emerge -puv portage |
27 |
> |
28 |
> These are the packages that would be merged, in order: |
29 |
> |
30 |
> Calculating dependencies... done! |
31 |
> |
32 |
> Total: 0 packages, Size of downloads: 0 kB |
33 |
> |
34 |
> So why doesn't it list the upgrade part now? |
35 |
|
36 |
Because --update stops calculating deps when none of the specified targets |
37 |
need updating. Only --deep checks the consistency of all dependencies even |
38 |
when none of the targets need updating. You could argue it's a deficiency in |
39 |
portage (although well-known).. |
40 |
|
41 |
-- |
42 |
Bo Andresen |