On Wednesday 22 June 2011 11:31:09 Daniel Pielmeier did opine thusly: > 2011/6/22 Alan McKinnon <alan.mckin...@gmail.com>: > > On Wednesday 22 June 2011 10:49:04 Daniel Pielmeier did opine thusly: > >> I guess it displays the USE settings how they should be and > >> afterwards prints the required changes. Or does it build fltk > >> with USE="-cairo" if you just type emerge -av fltk? > > > > emerge -av fltk > > > > gives exactly the same output as above. The dillo ebuild doesn't > > seem to be causing this change in behaviour: > > > > RDEPEND="x11-libs/fltk:2[-cairo,jpeg=,png=] > > > > What it looks like is portage is insisting the package.use > > explicitly states the USE flags needed. This is wrong and I am > > not about to bloat package.use to cater for every "built with > > use" occurrence. Or perhaps it's now only looking at installed > > deps and not it's own dep graph when emerge runs. > > > > Portage should only care about whether the package is already > > built with use, or will be according to the dep graph > > So you get the same recommendation about the use flag change?
No, I meant the output was the same as: [ebuild N ] x11-libs/fltk-2.0_pre6970-r1 USE="jpeg opengl png xft xinerama zlib -cairo -debug -doc" 2,470 kB I didn't run an emerge -p dillo to see what that would do, I did meanwhile add an entry to package.use to make portage shut up and do what I want (install claws) > If you have USE="cairo" in make.conf or it is enabled via some > profile (desktop?) you have to add >=x11-libs/fltk-2.0_pre6970-r1 > -cairo to package.use to override this on a per package basis. I > think there is no way around this. I have only the defaults: # grep -r cairo /etc/portage/* /etc/portage/package.use/package.use:x11-libs/cairo cleartype lcdfilter -qt4 /etc/portage/package.use/package.use:>=x11-libs/fltk-2.0_pre6970-r1 - cairo /etc/make.profile -> ../var/portage/profiles/default/linux/amd64/10.0/desktop # emerge --info | grep cairo USE=" ... cairo ... " The package.use entry is new. I still don't understand why portage is making this fuss. It is saying that fltk needs to have a package.use entry for -cairo, but that's not what it needs. It needs fltk *built* that way, becuase dillo requires it and claws-mail depends on dillo. Portage's own output immediately prior clearly says that it will build fltk with USE=-cairo as part of the dependencies. This crap about package.use is a red herring, a new behaviour and rather unwanted actually. It's adding useless new stuff into the process that doesn't belong. -- alan dot mckinnon at gmail dot com
