Summary: | sys-apps/portage: emerge should automatically skip fetch restricted packages if restriction is not solved | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Pacho Ramos <pacho> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | enhancement | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pacho Ramos
2012-05-28 09:30:10 UTC
You could use --keep-going. Do you want a separate option just for fetch failures? I use it, the problem is that even with that emerge tries to merge a package that will surely fail (as fetch restriction wasn't solved) and, then, exit with error status causing other concatenated commands (with &&) to fail (revdep-rebuild, emerge -a --depclean...) We could add a special option that prevents fetch restricted packages from affecting the return code of emerge when they can't be fetched. Alternatively, we could add an ACCEPT_RESTRICT variable that you could use like ACCEPT_PROPERTIES to mask fetch restricted packages. |