Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 260225 - emerge should have an option to automatically avoid redundant upgrades
Summary: emerge should have an option to automatically avoid redundant upgrades
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Server (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Portage team
Depends on: 1343
Blocks: 155723
  Show dependency tree
Reported: 2009-02-25 10:47 UTC by Alessandro Molina
Modified: 2011-09-20 18:14 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Alessandro Molina 2009-02-25 10:47:53 UTC
emerge -pv plone will result in
[ebuild  N    ] net-zope/zope-3.3.1  6,440 kB
[ebuild  N    ] net-zope/zope-2.10.7  7,099 kB
[ebuild  N    ] media-gfx/xv-3.10a-r15  USE="jpeg png tiff" 3,539 kB
[ebuild  N    ] app-admin/zope-config-0.6  0 kB
[ebuild  N    ] app-admin/zprod-manager-0.3.3  0 kB
[ebuild  N    ] dev-python/imaging-1.1.6  USE="X examples -doc -scanner -tk" 426 kB
[ebuild  N    ] net-zope/plone-3.1.7  12,487 kB

It isn't necessary to install both Zope3 and Zope2, this can be resolved by installing by hand zope2 and then by installing plone, which will result in plone not needing zope3 anymore as it needs "a zope release" and we just installed zope2.

Plone package should prevent zope-config from installing zope3 as plone package itself is already installing zope2.

Reproducible: Always

Steps to Reproduce:
1.emerge -pv plone (and you will see that zope3 will be requested)
2.emerge =zope-2.10.7
3.emerge -pv plone (and you will see that zope3 is not requested anymore)
Comment 1 Tupone Alfredo gentoo-dev 2009-02-27 09:14:22 UTC
Too hard to fix by me. 

What happens is that some packages ask to emerge a version of net-zope/zope, putting constraints on the version, and some just ask for "any" version of it.

Portage includes both a constrained version and the last allowed version, as they are slotted, and so they can live together.

Removing the slotting could, maybe, fix it. But then you cannot have more then one zope version on your computer.

Adding portage developers to CC, so maybe I could have some guideline.

For now, you can just mask net-zope/zope-3* by adding
>=net-zope/zope-3 in etc/portage/package.mask
Comment 2 Zac Medico gentoo-dev 2009-02-27 17:54:44 UTC
The sort of behavior that you want could be implemented in emerge as an 'avoid redundant upgrades' algorithm, so I'll reassign.
Comment 3 Zac Medico gentoo-dev 2011-09-20 18:14:05 UTC
If we don't pull in new slots, you'll never get the new versions, and newer versions are typically preferred. So, I think it's better to leave it to individuals to use a local package.mask if they feel that a new version is unnecessary.