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