1 |
On 03/17/12 15:43, Kent Fredric wrote: |
2 |
> On 18 March 2012 08:33, Matt Turner <mattst88@g.o> wrote: |
3 |
>> So you run set FEATURES=test to run a package's test suite during |
4 |
>> keywording. Later, you emerge -vuNDa ... and portage wants to reemerge |
5 |
>> that package with USE=-test. |
6 |
>> |
7 |
>> Can't we avoid this somehow? I presume in the vast majority of cases |
8 |
>> emerging with FEATURES/USE=test doesn't actually affect what's |
9 |
>> installed. |
10 |
> |
11 |
> Not so, there are a lot of things where USE="test" pulls in extra |
12 |
> dependencies, dev-perl/* is rife with them. |
13 |
> |
14 |
> And I've seen some things where USE=test changes behaviour of the |
15 |
> compile phase sufficient that enabling USE=test *could* change the |
16 |
> code compiled as well. |
17 |
|
18 |
To expand on this, I know that sys-devel/gcc will save a report of the |
19 |
make check results to the filesystem when FEATURES=test is enabled. |