Summary: | emerge should have an option to automatically avoid redundant upgrades | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alessandro Molina <alessandro.molina> |
Component: | [OLD] Server | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | esigra, pacho |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 1343 | ||
Bug Blocks: | 155723 |
Description
Alessandro Molina
2009-02-25 10:47:53 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
The sort of behavior that you want could be implemented in emerge as an 'avoid redundant upgrades' algorithm, so I'll reassign. 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. |