Mike Gilbert wrote: > On Mon, Jul 20, 2015 at 6:05 PM, Dale <[email protected]> wrote: >> Mike Gilbert wrote: >>> On Mon, Jul 20, 2015 at 4:45 PM, Dale <[email protected]> wrote: >>>> As you say, this makes no sense. It's like running in circles or >>>> something. Mostly or something. >>>> >>>> If you need more info, let me know. I'm pretty much clueless here. >>>> >>> What do you have in ACCEPT_KEYWORDS? Are you mixing arch and ~arch packages? >>> >>> If so, please make sure you have all of the following in pacakge.keywords: >>> >>> sys-fs/eudev >>> virtual/libgudev >>> dev-libs/libgudev >>> >>> For more information, see bug 552036. >>> >>> https://bugs.gentoo.org/show_bug.cgi?id=552036 >>> >>> >> >> That fixed it. I had eudev in there already. I had to because when it >> first came out, they were all keyworded. I didn't have the other two in >> there tho. I just wonder, why didn't portage figure that out? Oh well. > Portage tries very hard not to install new packages when attempting to > satisfy an || dep, especially when doing so would involve changing USE > flags. When it has no other choice, it sometimes picks the wrong || > dep to satisfy. > > In this case, it was trying to solve the conflict by switching from > eudev to static-dev, instead of installing libgudev. By upgrading to > virtual/libgudev-230, we remove that possibility from its set of > possible solutions. > >
I figured it had some reason for it. Based on my thinking, it can only present one option. Maybe one day some more can be added but in the meantime, I'm not complaining. Dale :-) :-)
