| Summary: | auxdbkeys DEFINED_PHASES only shows test if there is a explicit src_test | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | APN-Pucky <alexander> |
| Component: | Core - External Interaction | Assignee: | Portage team <dev-portage> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | alexander |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
This behaviour is quite contradicting since if I add
src_test() {
default
}
to the ebuild it shows up with a defined test phase. Contrary ebuilds that inherit e.g. distutils-r1 are reported with a defined test phase too regardless of disturils_enable_tests being set or not.
|
Background is pkg-testing-tools uses >>> portage.portdb.aux_get("sci-physics/rivet-3.1.10", ["DEFINED_PHASES"]) ['configure install prepare setup'] to identify if a package has a test stage. Here rivet does not provide a explicit src_test function. However running $ ebuild rivet-3.1.10.ebuild test will execute some default/inherited test routine. Is there another recommended way to check if a packages supports the test feature?