Paweł Hajdan, Jr. posted on Mon, 24 Oct 2011 08:58:57 +0200 as excerpted: > Third - can we forcefully disable hardened features in packages that are > not compatible? My assumption is yes, and we should probably print a > warning then.
If a warning is to be printed (and I agree that's a good idea), please arrange for it to be disableable per-package (perhaps via environmental variable setting, WARN_DISABLE_HARDENED or the like). That way, either the PM can implement a package.hardened-warn or whatever, or (for portage at least) the user can arrange for the same effect via /etc/portage/env/*/* files. The idea would be that the user can accumulate an easily checked list of packages he knows about and doesn't want to be bothered by the hardened- disable warnings for, while he still gets visible warnings for packages not on that list (and thus presumably that he's not yet aware of) that disable whatever hardening feature. Or just make it a USE flag on the packages it applies to: hardened-warn or the like, which use-defaults to ON. Either way, an eclass to standardize things sounds very useful. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
