On Wed, Aug 15, 2012 at 3:26 PM, Ciaran McCreesh <ciaran.mccre...@googlemail.com> wrote: > On Wed, 15 Aug 2012 15:18:24 -0400 > Michael Mol <mike...@gmail.com> wrote: >> I've occasionally noticed portage tell me about circular dependencies, >> where the most straight forward resolution is to emerge some package >> in the loop twice. The first time, with a USE flag disabled (avahi and >> gtk are the usual suspects), and the second time with the USE flag >> enabled. >> >> In circumstances where it's necessary to do something like that to >> reach a final desired system state, I'm not sure I see any problem >> with portage automatically doing the two-stage emerge. > > That's going to be rather horrible when your package mangler > "temporarily" turns off acl or turns on build...
Fair observation; there would need to be a way either weight benign or dangerous USE/package flags, and search paths with weights outside of a 'safe' range would be discarded. A mechanism like that also offers a means of finding and favoring cheap rebuilds over expensive ones; rebuilding gcc an extra time ought to be disfavored over rebuilding, say, sudo. -- :wq
