On 03/17/2012 12:51 PM, Alexandre Rostovtsev wrote:
> I think the easier solution is to modify portage to ignore changes in
> the "test" USE flag when doing "emerge --newuse".
Yes, that's part of the plan [1] discussed in bug #373209.
[1] https://bugs.gentoo.org/show_bug.cgi?id=373209#c3
--
Than
On Sat, 2012-03-17 at 15:33 -0400, Matt Turner wrote:
> So you run set FEATURES=test to run a package's test suite during
> keywording. Later, you emerge -vuNDa ... and portage wants to reemerge
> that package with USE=-test.
>
> Can't we avoid this somehow? I presume in the vast majority of cases
On 03/17/12 15:43, Kent Fredric wrote:
> On 18 March 2012 08:33, Matt Turner wrote:
>> So you run set FEATURES=test to run a package's test suite during
>> keywording. Later, you emerge -vuNDa ... and portage wants to reemerge
>> that package with USE=-test.
>>
>> Can't we avoid this somehow? I pr
On 18 March 2012 08:33, Matt Turner wrote:
> So you run set FEATURES=test to run a package's test suite during
> keywording. Later, you emerge -vuNDa ... and portage wants to reemerge
> that package with USE=-test.
>
> Can't we avoid this somehow? I presume in the vast majority of cases
> emerging
On Sat, 17 Mar 2012 15:33:42 -0400
Matt Turner wrote:
> So you run set FEATURES=test to run a package's test suite during
> keywording. Later, you emerge -vuNDa ... and portage wants to reemerge
> that package with USE=-test.
>
> Can't we avoid this somehow? I presume in the vast majority of case
So you run set FEATURES=test to run a package's test suite during
keywording. Later, you emerge -vuNDa ... and portage wants to reemerge
that package with USE=-test.
Can't we avoid this somehow? I presume in the vast majority of cases
emerging with FEATURES/USE=test doesn't actually affect what's
