Summary: | Request of adding feature to a portage - automatical fall back to older ebuilds of any problem occures | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jacek Mateusz 'daeron' Ławrynowicz <daeron> |
Component: | [OLD] Development | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | esigra, pacho |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 1343 | ||
Bug Blocks: | 155723 |
Description
Jacek Mateusz 'daeron' Ławrynowicz
2009-02-26 09:39:09 UTC
It's not supported yet. We still need to implement backtracking in the dependency resolver. I think the current behavior is what people usually want, namely that packages use the highest version of their dependency. In the rare cases you want to diverge from that, p.mask is imo an acceptable solution. (In reply to comment #0) > After messing up with layman I was looking for a feature that'd let portage > automatically fall back to older ebuild version if any problem, like > missing/masked dependencies, occures. > That feature would have 2 levels > 1. It'd use older version if dependencies couldn't be met This is implemented with backtracking since portage-2.1.9. > 2. It'd use older version if emerge fails. Use emerge --keep-going, and add failed packages to package.mask as suggested in comment #2. *** This bug has been marked as a duplicate of bug 300071 *** |