| 1 |
2011/6/22 Neil Bothwick <neil@××××××××××.uk>: |
| 2 |
> On Wed, 22 Jun 2011 10:18:05 +0200, Alan McKinnon wrote: |
| 3 |
> |
| 4 |
>> The following USE changes are necessary to proceed: |
| 5 |
>> #required by www-client/dillo-2.2, required by mail-client/claws- |
| 6 |
>> mail-3.7.9-r1[dillo], required by claws-mail (argument) |
| 7 |
>> >=x11-libs/fltk-2.0_pre6970-r1 -cairo |
| 8 |
> |
| 9 |
>> Any reason why portage is telling me to set a USE that is already |
| 10 |
>> there per portage's own output? |
| 11 |
> |
| 12 |
> As Daniel said, this is what portage needs, it's been that way since the |
| 13 |
> autounmask stuff was introduced. Or you could emerge Claws with -dillo |
| 14 |
> and use the fancy plugin for HTML rendering. I stopped using the dillo |
| 15 |
> renderer years ago. |
| 16 |
|
| 17 |
Actually it is like that since the introduction of use-dependencies |
| 18 |
like cat/pkg-ver[use] and _before_. Autounmask ist just for the users |
| 19 |
convenience to copy paste the needed changes to package.use. I guess |
| 20 |
the reason for this coming up more often is that develpopers start to |
| 21 |
use use-dependencies more often. |
| 22 |
|
| 23 |
Before the introduction of use dependencies the only possible way was |
| 24 |
to stop emerge at build time and tell the user he needs USE="X" for |
| 25 |
package Y. With use dependencies it is now possible to inform the user |
| 26 |
about it when resolving the dependencies. |
| 27 |
|
| 28 |
So nothing has changed. If a package requires use settings which are |
| 29 |
different from the defaults you have to override this on a per package |
| 30 |
basis via package.use. |
| 31 |
|
| 32 |
-- |
| 33 |
Regards, |
| 34 |
Daniel |
Archives