Re: [gentoo-dev] turning off a default compile option

[Grant Goodyear]

> The user would like a way to disable linux compatability if your kernel
> does not support it by using the 'caps' use flag. Maybe I dont fully
> understand 'linux compatability' but if we're all running Gentoo, arent
> we all running linux in the first place?

It's "capabilities", not "compatability [sic]".  My understanding 
is that capabilities allow for partitioning of root's all-powerful
nature into fine-grained permissions.  Thus, obtaining root is no longer
sufficient to do massive harm.  I believe this notion is central to
selinux, but I'm not sure if anything else uses it at the moment.

> My problem surfaces: Bind enables 'linux compatability' by default.
> Gentoo does have a linux compability flag (caps), but this is only to
> ENABLE linux compatability, not to disable it. I attempted to use the
> bugger's suggestion, but repoman got pissed on a full scan. Grant
> mentioned maybe making 'caps' part of the default use flag.

Actually, what I said is that capabilities should be disabled _unless_
USE=caps, and that if there seemed to be a broad need for capabilities
for our users then we might want to discuss making it a default USE
flag.

> Basically I'd like a way of using a "reverse" use flag, -caps, and if
> -caps is set, disable linux compat; if the flag is not set, do not add
> any --config-option at all.

I don't think a reverse flag is needed here.  The fact that bind only
has a --disable setting for capabilities and not an --enable is a bit
odd, but it doesn't require us to change how our USE flags work.  If
USE=caps, then no flag needs to be sent to configure (but comment the
ebuild so there's a record that bind's configure is warped), but if
"caps" is not in USE, then send the --disable.

Best,
g2boojum
-- 
Grant Goodyear	
Gentoo Developer
g2boojum@g.o
http://www.gentoo.org/~g2boojum
GPG Fingerprint: D706 9802 1663 DEF5 81B0  9573 A6DC 7152 E0F6 5B76