| Summary: | app-crypt/mit-krb5 - useless src_test() output | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jeroen Roovers (RETIRED) <jer> |
| Component: | Current packages | Assignee: | Gentoo Kerberos Maintainers <kerberos> |
| Status: | RESOLVED FIXED | ||
| Severity: | QA | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
That work around predates me. I'll see what I can do. Thanks for the pointers. +*mit-krb5-1.9_beta1 (24 Nov 2010) + + 24 Nov 2010; Eray Aslan <eras@gentoo.org> +mit-krb5-1.9_beta1.ebuild, + metadata.xml: + Version bump. Dropped m68k bug #324087. Working test suite bug #346549. + Added test and pkinit USE flags. + Will also add a working test suite to mit-krb5-1.8 branch if/when there is a bump (patch is ready). Thanks again. |
src_test() { einfo "Tests do not run in sandbox, they need mit-krb5 to be already installed to test it." } I don't get this. I assume that, with the above output, it knows I initially had FEATURES=sandbox and that the same version wasn't yet installed. So I emerged it again with FEATURES=-sandbox, assuming the test suite would now be run. That's when I looked at the ebuild and found the above. You could look at what other packages do, like imagemagick, to work around the install-before-test problem, and you could perhaps run the test suite regardless of FEATURES=sandbox and just warn that it might fail.