| 1 |
On Wednesday 22 June 2011 10:49:04 Daniel Pielmeier did opine thusly: |
| 2 |
> 2011/6/22 Alan McKinnon <alan.mckinnon@×××××.com>: |
| 3 |
> > # emerge -av claws-mail |
| 4 |
> > |
| 5 |
> > These are the packages that would be merged, in order: |
| 6 |
> > |
| 7 |
> > Calculating dependencies... done! |
| 8 |
> > [ebuild N ] net-libs/libetpan-1.0 USE="berkdb gnutls sasl |
| 9 |
> > ssl - debug -ipv6 -liblockfile" 1,631 kB |
| 10 |
> > [ebuild N ] x11-libs/fltk-2.0_pre6970-r1 USE="jpeg opengl |
| 11 |
> > png xft xinerama zlib -cairo -debug -doc" 2,470 kB |
| 12 |
> > [ebuild N ] www-client/dillo-2.2 USE="gif jpeg png ssl |
| 13 |
> > -doc - ipv6" 616 kB |
| 14 |
> > [ebuild N ] mail-client/claws-mail-3.7.9-r1 USE="crypt |
| 15 |
> > dbus |
| 16 |
> > dillo gnutls imap ldap session spell ssl startup-notification - |
| 17 |
> > bogofilter -doc -ipv6 -nntp -pda -smime -spamassassin -xface" |
| 18 |
> > 6,921 kB |
| 19 |
> > |
| 20 |
> > Total: 4 packages (4 new), Size of downloads: 11,637 kB |
| 21 |
> > |
| 22 |
> > The following USE changes are necessary to proceed: |
| 23 |
> > #required by www-client/dillo-2.2, required by |
| 24 |
> > mail-client/claws- |
| 25 |
> > mail-3.7.9-r1[dillo], required by claws-mail (argument) |
| 26 |
> > |
| 27 |
> >>=x11-libs/fltk-2.0_pre6970-r1 -cairo |
| 28 |
> >> |
| 29 |
> > Any reason why portage is telling me to set a USE that is |
| 30 |
> > already |
| 31 |
> > there per portage's own output? |
| 32 |
> > |
| 33 |
> > It will build fltk with USE=-cairo, so why the need to tell me |
| 34 |
> > to set it explicitly? |
| 35 |
> |
| 36 |
> I guess it displays the USE settings how they should be and |
| 37 |
> afterwards prints the required changes. Or does it build fltk with |
| 38 |
> USE="-cairo" if you just type emerge -av fltk? |
| 39 |
|
| 40 |
emerge -av fltk |
| 41 |
|
| 42 |
gives exactly the same output as above. The dillo ebuild doesn't seem |
| 43 |
to be causing this change in behaviour: |
| 44 |
|
| 45 |
RDEPEND="x11-libs/fltk:2[-cairo,jpeg=,png=] |
| 46 |
|
| 47 |
What it looks like is portage is insisting the package.use explicitly |
| 48 |
states the USE flags needed. This is wrong and I am not about to bloat |
| 49 |
package.use to cater for every "built with use" occurrence. Or perhaps |
| 50 |
it's now only looking at installed deps and not it's own dep graph |
| 51 |
when emerge runs. |
| 52 |
|
| 53 |
Portage should only care about whether the package is already built |
| 54 |
with use, or will be according to the dep graph |
| 55 |
|
| 56 |
|
| 57 |
-- |
| 58 |
alan dot mckinnon at gmail dot com |
Archives