| 1 |
2011/6/22 Alan McKinnon <alan.mckinnon@×××××.com>: |
| 2 |
> On Wednesday 22 June 2011 10:49:04 Daniel Pielmeier did opine thusly: |
| 3 |
>> |
| 4 |
>> I guess it displays the USE settings how they should be and |
| 5 |
>> afterwards prints the required changes. Or does it build fltk with |
| 6 |
>> USE="-cairo" if you just type emerge -av fltk? |
| 7 |
> |
| 8 |
> emerge -av fltk |
| 9 |
> |
| 10 |
> gives exactly the same output as above. The dillo ebuild doesn't seem |
| 11 |
> to be causing this change in behaviour: |
| 12 |
> |
| 13 |
> RDEPEND="x11-libs/fltk:2[-cairo,jpeg=,png=] |
| 14 |
> |
| 15 |
> What it looks like is portage is insisting the package.use explicitly |
| 16 |
> states the USE flags needed. This is wrong and I am not about to bloat |
| 17 |
> package.use to cater for every "built with use" occurrence. Or perhaps |
| 18 |
> it's now only looking at installed deps and not it's own dep graph |
| 19 |
> when emerge runs. |
| 20 |
> |
| 21 |
> Portage should only care about whether the package is already built |
| 22 |
> with use, or will be according to the dep graph |
| 23 |
|
| 24 |
So you get the same recommendation about the use flag change? |
| 25 |
|
| 26 |
If you have USE="cairo" in make.conf or it is enabled via some profile |
| 27 |
(desktop?) you have to add >=x11-libs/fltk-2.0_pre6970-r1 -cairo to |
| 28 |
package.use to override this on a per package basis. I think there is |
| 29 |
no way around this. |
| 30 |
|
| 31 |
-- |
| 32 |
Regards, |
| 33 |
Daniel |
Archives