Summary: | revdep-rebuild doens't rebuild unstable ebuilds | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Carsten Lohrke (RETIRED) <carlo> |
Component: | Tools | Assignee: | Portage Tools Team <tools-portage> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Carsten Lohrke (RETIRED)
2004-01-15 09:32:41 UTC
use package.keywords in 2.0.50 *** This bug has been marked as a duplicate of 13616 *** Marius, may I ask, why not adding my proposed fix? It wouldn't harm and works with the current portage. Another one: =category/ebuild-1.2.3-r1 revdep-rebuild fails, if ebuild-1.2.3-r1 doesn't exist anymore in portage. Not very smart. Because you suggestion would be a fix for one (common) case but would cause breakage/unexpected behavior in some other cases, e.g. the --package-names option would behave differently. Uh, sure - in this special case it shouldn't be done. But is it that hard to test if the current ebuild is preceeded by "=". In this case there is nothing else expected, than: - emerge it, if the ebuild exists - don't care about ~/arch - smart handling of non-existing ebuilds e.g. --force option -> using --package-names ebuildname instead or just drop the ebuild in favor of the rest of ebuilds and give a list of the failed ones back Non-existant issue with current portage versions. |