| 1 |
On Wednesday 22 June 2011 10:47:54 Neil Bothwick did opine thusly: |
| 2 |
> On Wed, 22 Jun 2011 10:18:05 +0200, Alan McKinnon wrote: |
| 3 |
> > The following USE changes are necessary to proceed: |
| 4 |
> > #required by www-client/dillo-2.2, required by |
| 5 |
> > mail-client/claws- |
| 6 |
> > mail-3.7.9-r1[dillo], required by claws-mail (argument) |
| 7 |
> > |
| 8 |
> > >=x11-libs/fltk-2.0_pre6970-r1 -cairo |
| 9 |
> > |
| 10 |
> > Any reason why portage is telling me to set a USE that is |
| 11 |
> > already |
| 12 |
> > there per portage's own output? |
| 13 |
> |
| 14 |
> As Daniel said, this is what portage needs, it's been that way since |
| 15 |
> the autounmask stuff was introduced. |
| 16 |
|
| 17 |
In other words, we must now all end up with giganticly bloated |
| 18 |
package.use files to satisfy every "built with use" requirement |
| 19 |
system-wide? What's wrong with looking at the defaults and saying |
| 20 |
"Gee, you know what, the implicit rules on the box are going to do the |
| 21 |
right thing anyway, so let's proceed and build the stuff?" |
| 22 |
|
| 23 |
> Or you could emerge Claws with |
| 24 |
> -dillo and use the fancy plugin for HTML rendering. I stopped using |
| 25 |
> the dillo renderer years ago. |
| 26 |
|
| 27 |
Well, that's an option. |
| 28 |
|
| 29 |
But I fear this behaviour is going to rear it's head many more times |
| 30 |
with other ebuilds. |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
alan dot mckinnon at gmail dot com |
Archives