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