Summary: | sys-apps/portage: --usepkg does not respect FEATURES="test" | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Michael Seifert <m.seifert> |
Component: | Binary packages support | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | esigra |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=639588 https://bugs.gentoo.org/show_bug.cgi?id=832168 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 639588, 912975 |
Description
Michael Seifert
2017-11-29 13:36:53 UTC
(In reply to Michael Seifert from comment #0) > Expected Results: > Emerge ignores the existing binary due to different USE configuration (since > --binpkg-respect-use is enabled by default) and builds the package from > source with USE="test". It's not intended to work that way. The assumption is that you would not use --usepkg if you wanted to run unit tests. The link between FEATURES=test and USE=test is unfortunate. It would be nice if we could eliminate it somehow. For example, we could introduce a separate variable for test dependencies, and provide some way for the ebuild to know in earlier phases if src_test is to be executed later (in case the early phases need to make some adjustments for this). I understand that USE="test" is somewhat special. I already thought that I might be misusing portage :) My main goal was to install the test dependencies. Shouldn't --with-test-deps=y do the trick (except running src_test)? As I mentioned in parentheses, it doesn't seem to pull in the test dependencies in the same setup. Yet, I'd expect it to do exactly that. (Or should this be a different ticket?) Yes please file a new ticket for the --with-test-deps=y option which currently has no effect on binary packages. Currently, the only way to include test dependencies for binary packages is to build them with USE=test enabled *and* use the --with-bdeps=y option. Will do so, thanks! Do you think it makes sense to add a line about the interaction of --usepkg and USE="test" in the documentation of the --usepkg switch? I debugged this for around two days, until I knew what was going on and had a minimal example. Maybe this will prevent someone else from running into it. Yes, a mention in the documentation is a very good idea. (In reply to Zac Medico from comment #1) > (In reply to Michael Seifert from comment #0) > > The link between FEATURES=test and USE=test is unfortunate. It would be nice > if we could eliminate it somehow. For example, we could introduce a separate > variable for test dependencies, and provide some way for the ebuild to know > in earlier phases if src_test is to be executed later (in case the early > phases need to make some adjustments for this). Factoring out test dependencies into a new ebuild variable sounds like a very good idea. It also seems like a logical thing to do, now that host and target dependencies for cross-compilation are being separated in EAPI 7. Is there a bug or GLEP to track the progress on the "TDEPEND" idea? There is bug 517658, but it's focused on circular dependency issues, so we need to open a separate bug. |