Summary: | merge test deps for a package without merging their test deps or running their tests | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Patrick McLean <chutzpah> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | esigra, wizardedit |
Priority: | Normal | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 155723, 484436 |
Description
Patrick McLean
2014-08-22 22:38:33 UTC
(In reply to Patrick McLean from comment #0) > Perhaps something along the lines of FEATURES=testdeps that makes it portage > pull in only test deps for stuff on the command line. Is it okay for emerge to remove these test deps when you run emerge --depclean, or in order to solve a blocker conflict encountered when updating your system? If it's not okay to remove them, then we need to specify precisely how they are supposed to be pulled into the dependency graph during future dependency calculations. That would be fine, they could be merged as if I did an "emerge -1" on them. Basically I am looking for an easy way to get the test deps without getting the test deps for the test deps or running tests on the whole tree. Another use for this is automated ebuild testing of specific packages. Based on irc discussion, the plan is to add a new emerge --with-test-deps option which causes test dependencies to get pulled just for packages matched by emerge arguments. For example, the following command will install the regular dependencies of "foo" as well as the direct test dependencies of "foo": emerge --onlydeps --with-test-deps foo I have a patch in the following branch: https://github.com/zmedico/portage/tree/bug_520652 I've posted it for review here: http://thread.gmane.org/gmane.linux.gentoo.portage.devel/4760 This is in the master branch now: https://github.com/gentoo/portage/commit/6205081cd90b94ccb12d17784c12b31229eb6b3c Fixed in 2.2.15. |