Summary: | debug eclass usability and global inherit | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Jeremy Huddleston (RETIRED) <eradicator> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jeremy Huddleston (RETIRED)
2003-12-14 15:49:56 UTC
Wrapping an inherit call in bash conditionals isn't supported. And 'if use debug' is prefered to using a [ "" ] style. As far as it working, it should, although it violates DB key limitations. Try it per normal. You can always specify CFLAGS in your make.conf or command line. Uhm... I don't think you got what I'm saying here... it's simply a feature request, so I know it can't be done in current portage, but I think it would be useful (maybe something for portage-ng if it is too much for current portage). The debug eclass is not automatically inherited when the debug use flag is active, but it would be nice to have it automatically inherited (or atleast the option to). As for putting the CFLAGS in make.conf or in the environment when calling emerge, I know about that, but as I showed that is very limiting. It would be nice to have a way to setup different CFLAGS (and other variables) based on the package or USE flags. Make the eclass handle the flag. INHERIT is a DB key. It cannot be conditionalized. Submit the "inherit wherever/however I please" to either the portage-ng list if you really have reason/motive to have it added. I do not like the idea. |