sys-fs/udev:extras - Compile udev-extras requiring external dependencies 1) What does that mean, really? 2) Why aren't these dependencies offered with their own USE flag? 3) But mainly, can we separate sys-apps/acl out so we can fix bug #212517 by masking the new USE=acl and still keep usbutils/pciutils? 4) Or alternatively, is there a timeframe for a non-USE=extras ebuild to go stable? Some newer ebuilds do not seem to use it anymore.
Actually, this was already done - 'extras' is just a legacy flags (taking a look at the ebuild/ChangeLog should give you hint): ChangeLog entry 05 Jun 2011, bug 348472.
but reading more into bug #212517, I'm suspecting a hardware/arch specific problem. After all, acl/xattr has been the backend of policykit for quite awhile and this has obviously been working for a lot of people (let's see: udisks, upower, pulseaudio, etc.).
(In reply to comment #2) > but reading more into bug #212517, I'm suspecting a hardware/arch specific > problem. ACL/XATTR were never ported to HPPA, so they always return ENOSYS and other funny stuff. Some software actually breaks when used as the ENOSYS case isn't considered. Hence the blocked bug report.
The extras use flag was removed in udev-175. However, that version of udev is hard masked (see the package.mask file for an explanation). It is supported along with separate use flags in udev-171-r2, which I am considering stabilizing. There are a couple of bugs against it that I want to look at though.
udev-171-r3 just went into the tree. The difference between it and -r2 is that the startup scripts received a significant update, so I'll give that a few days and if there are no issues I'll request stabilization.
This looks fixed now: 1. gentoo-x86/profiles/arch/hppa/use.mask:acl 2. USE="acl" in udev-171-r5 and USE="extras" entirely gone in the current ~arch version, udev-181, which should be the next stable target sometime later
