On 11/08/13 08:36, Walter Dnes wrote:
On Sat, Aug 10, 2013 at 09:57:52AM +0300, Samuli Suominen wrote
I expect it to happen around every new udev release that causes slight
incompability; the default of the virtual/udev, sys-fs/udev, doesn't
have to wait for the alternative providers.
The elegant solution is outlined in my post...
http://www.gossamer-threads.com/lists/gentoo/user/275977#275977
I.e. *UNTIL SUCH TIME AS EUDEV HITS STABLE* (on whatever arch you're
using), add the entry
<sys-fs/eudev-9999 ~amd64
to package.keywords (replace amd64 with your arch if necessary).
Basically, if you keyword a specific version, and the ebuild gets
removed by "emerge --sync", there are no eudev ebuilds to satisfy
virtual/udev. So portage falls back to udev. My solution isn't
hard-coded to any one version, and is immune to to version bumps and
removals.
bad idea to unmask "the new multilib eudev" on stable, regarding
blockers it has like
"!<=app-emulation/emul-linux-x86-baselibs-20130224-r7" on amd64 multilib
when ABI_X86="32" is enabled
as in, unresolvable dependencies
