betelgeuse@pena /usr/portage/dev-libs/DirectFB $ euse -i sysfs global use flags (searching: sysfs) ************************************************************ no matching entries found local use flags (searching: sysfs) ************************************************************ [- ] sysfs (dev-libs/DirectFB): Add support for the sysfs filesystem (requires Linux-2.6+) [- ] sysfs (net-misc/bridge-utils): Enable use of the sysfs filesystem (Linux-2.6+) via libsysfs This should be on by default in profiles for 2.6 kernels I think. CCing all people who I think maintain profiles as I think there is no common parent to do this in but please correct me if I am wrong or missed someone.
We don't care at the moment, none of the packages you mention is keyworded for sparc (actually they're quite broken!)
The two packages listed here don't really have a use on mips for the time being. Our frame buffer devices are about as unique as things can get, and I have never tested wireless. We'll bypass for now.
ppc-macos doesn't have a linux kernel, so this doesn't make sense to me.
On the hardened profiles we would rather let the users pick his/her own USE=flags vs forcing a bunch of what "we think". Unless omitting this flag causes breage in 'system' we would like to abstain from adding it globally.
Alpha is not interested as discussed in irc
(In reply to comment #5) > Alpha is not interested as discussed in irc > EDIT: We don't have a keyword for bridge-utils. Having only one package for a default flag is not what we want unless DirectFB would break.
I'm with Brian. Thanks.(In reply to comment #6) > (In reply to comment #5) > > Alpha is not interested as discussed in irc > > > > EDIT: We don't have a keyword for bridge-utils. Having only one package for a > default flag is not what we want unless DirectFB would break. > I'm with Brian. alpha is out. Thanks.
selinux profile now inherits from default-linux/$arch, so we automatically pick it up when the parent arches add it.
just drop it into default-linux/ and be done
For default-linux/x86 (no hardened) I think this sounds like a good idea, but mabye releng or others who really work on the profiles would like to comment here.
It might help to add us if you want us to answer... ;] Anyway, do not add something like this to default/x86. In fact, don't ever add *anything* regarding USE to default/$arch unless you want the wrath of the flying Release Engineering goats coming after you. :P If we were to introduce this, I would like to introduce it using the methods I've been using for new flags, which is to add it to the next release's profile, *even if it belongs lower* and moving it down the chain as the older profiles get deprecated/removed. This keeps new USE flags from popping on for the users while still allowing us to add new features with new releases. If nobody disagrees, I'd say remove arches from CC, and we'll add it into the next release and everybody will end up getting it over time. The sysfs USE flag should be masked on all of the 2.4 profiles already, anyway. If it isn't, that can be done now. Of course, this is also a local USE flag, which we normally don't enable. As others stated, is there something broken by this being off that would require us to enable it? I'd much rather simply not bother, especially as 2.4 support is ever-quickly disappearing from the tree.
Chris, Wise words. I like your proposal.
(In reply to comment #11) > If nobody disagrees, I'd say remove arches from CC, and we'll add it into the > next release and everybody will end up getting it over time. The sysfs USE > flag should be masked on all of the 2.4 profiles already, anyway. If it isn't, > that can be done now. It sounds good to me. Arches?
You're quite a bit too late. I've already started working on this in the 2007.1 snapshot. ;]
(Removing arches, since I'll take care of it all...)
Yeah, i was asking about unccing ;)
I apologize for letting this one slip by for 2008.0, but I've added it to the tree's /release/make.defaults, so it'll get pulled in automatically next release, too.
