Summary: | ruby-ng.eclass should not force adding 'test' to IUSE when adding an RDEPEND | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | konsolebox <konsolebox> |
Component: | Eclasses | Assignee: | Gentoo Ruby Team <ruby> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
konsolebox
2022-07-22 11:45:44 UTC
Last line should probably be placed inside the `if has test ...` block as well. The idea is that you always need runtime dependencies at test time so it's doing DEPEND="test? ( ${RDEPEND} )". Python packages do the same if using d_e_t. What problem are you trying to fix here? I'm not sure what problem the existing situation would cause or what approaches this would be blocking. (In reply to Sam James from comment #2) > The idea is that you always need runtime dependencies at test time so it's > doing DEPEND="test? ( ${RDEPEND} )". > > Python packages do the same if using d_e_t. That's ok but the problem is about test being forced as an IUSE even in packages that don't want or can't have it; not the dependencies being forced to 'test'. (In reply to Hans de Graaff from comment #3) > What problem are you trying to fix here? I'm not sure what problem the > existing situation would cause or what approaches this would be blocking. No situation. Just troublesome inconsistency that made me check the eclasses plenty of times already. If the ebuild doesn't provide a test, 'test' shouldn't be forced in it and appear in `emerge -v`. |