Summary: | `ebuild rpm' doesn't explicitly check for app-arch/rpm | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Sergey S. Starikoff <Ikonta> |
Component: | Tools | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sergey S. Starikoff
2010-11-01 06:21:56 UTC
USE flags for runtime dependencies are pointless as it was explained many times before. But sure, we could report an error more sane. (In reply to comment #1) > USE flags for runtime dependencies are pointless as it was explained many times > before. Excuse me. It is my mistake. > But sure, we could report an error more sane. > It will be good. But, I think, not only error message should be improved, but also the point of it's reporting: it should be reported before compillation starts. Maybe, the better solution will be to add 'rpm' USE for sys-apps/portage, with proper RDEPEND when this use enabled and disabling rpm command otherwise. (In reply to Sergey S. Starikoff from comment #3) > Maybe, the better solution will be to add 'rpm' USE for sys-apps/portage, > with proper RDEPEND when this use enabled and disabling rpm command > otherwise. Disabling stuff in like this in a python app doesn't make much sense. I would prefer that it check for the rpmbuild command earlier and bail out with a short error message when necessary. |