| Summary: | portage complains about 'automake --get-libdir' call | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Michał Górny <mgorny> |
| Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
| Status: | CONFIRMED --- | ||
| Severity: | minor | CC: | base-system, qa |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
adding a helper to autotools.eclass like automake_tool() should be fine. "$(automake_tool py-compile)" . || die (In reply to comment #1) > adding a helper to autotools.eclass like automake_tool() should be fine. > > "$(automake_tool py-compile)" . || die You mean: cp "$(automake_tool py-compile)" . || die Correct? Probably the name should have some 'get' or otherwise it suggests it calls it. (In reply to comment #2) yes, cp. in your snippet, i thought you were running `py-compile` and not just updating it locally. there is talk upstream of adding a dedicated command so you can automake to refresh/install its helper programs, but that doesn't seem to have gone anywhere. |
I've committed the following snippet to dev-python/subunit; DEPEND=">=sys-devel/automake-1.12" src_prepare() { # update py-compile to handle py3 properly cp "$(automake --print-libdir || die)"/py-compile . || die ... } And now portage complains that: * QA Notice: 'automake' called by src_prepare: dev-python/subunit-0.0.10-r1 * Use autotools.eclass instead of calling 'automake' directly. But is there anything autotools.eclass could help me with? I'm not reconfiguring the package, and I don't see any helper there which could be used to obtain automake's libdir.