On Sun, 21 Feb 2010 10:11:25 +0100 "Paweł Hajdan, Jr." <phajdan...@gentoo.org> wrote:
> On 2/21/10 5:08 AM, Ryan Hill wrote:
> > I have one simple request. When you make a non-trivial change to an ebuild
> > -
> > a patch, a version bump, anything that can effect the behaviour of the
> > package - please run the test suite.
>
> Yeah, on my dev box I just run with FEATURES="test" all the time. Then
> it's impossible to forget it. And I also catch failures in other packages.
>
> Maybe it should get more exposure in the developer docs?
It's enabled by default in the developer profiles, so either devs aren't using
them or they're explicitly disabling it.
> By the way, for packages that fail the test suite and refuse to disable
> it, I change the env locally so that FEATURES=-test (via /etc/portage/env).
I used to do exactly that but it has a big disadvantage. There are
particular packages where I want to disable the test USE flag simply because
it pulls in a ton of unwanted dependencies. This can't be done with env
files; it's force {en,dis}abled by the global FEATURES setting (even
package.use doesn't override it).
Luckily, you can kill two birds with one stone by using a little trick buried
deep in the make.conf manpage: masking the test USE flag for a particular
package disables the test suite /even if that package doesn't have a test USE
flag/.
$ head -n5 /etc/portage/profile/package.use.mask
dev-db/virtuoso-server test
dev-java/commons-cli test
dev-libs/boost test
dev-libs/ppl test
dev-util/subversion test
--
fonts, by design, by neglect
gcc-porting, for a fact or just for effect
wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
signature.asc
Description: PGP signature
