On 8/5/07, Tim Allingham <[EMAIL PROTECTED]> wrote: > > On Sun, 2007-08-05 at 16:32 +0200, Bo Ørsted Andresen wrote: > > On Tuesday 17 July 2007 00:46:08 maxim wexler wrote: > > > So, emerge portage results in one package being > > > installed, portage, 61kb. > > > > > > emerge -u portage lines up 5 or 6 packages plus > > > portage, 18Mb. > > > > > > Went ahead and just did the one package, figuring > > > later I could do an emerge -u for the rest of it. > > > > > > But this is what happens: > > > > > > [EMAIL PROTECTED] ~ $ emerge -pv portage > > > > > > These are the packages that would be merged, in order: > > > > > > Calculating dependencies... done! > > > [ebuild R ] sys-apps/portage-2.1.2.9 USE="-build > > > -doc -epydoc (-selinux)" LINGUAS="-pl" 0 kB > > > > > > Total: 1 package (1 reinstall), Size of downloads: 0 > > > kB > > > > > > What I expected. > > > > > > [EMAIL PROTECTED] ~ $ emerge -puv portage > > > > > > These are the packages that would be merged, in order: > > > > > > Calculating dependencies... done! > > > > > > Total: 0 packages, Size of downloads: 0 kB > > > > > > So why doesn't it list the upgrade part now? > > > > Because --update stops calculating deps when none of the specified > targets > > need updating. Only --deep checks the consistency of all dependencies > even > > when none of the targets need updating. You could argue it's a > deficiency in > > portage (although well-known).. > > > > meaning that an emerge -pvuD world/portage should show the upgrades > > I just use emerge -DNavu world (can always substitute -p in there for emerge -DNpvu world) - helps to make sure all packages are up to date, including use flags for those packages.
-- - Mark Shields
