On Thu, May 31, 2007 at 06:15:07PM -0400, Thor Lancelot Simon wrote: > > While talking about this change, it is too late to change the option > > name to "USE_FORTIFY"? I can't see any reason for using the abbreviated > > "FORT" in the name. > > It's long and ungainly and there's something else called FORTIFY (worse, > I suspect it's trademarked). But USE_FORTIFY_SOURCE is even worse. Hm. Most (all?) of our other user-accessible build knobs are of the form MKFOO, and some of those then in turn imply different USE_FOO and other options around the tree. What about something like MKHARDENED that a user can set in mk.conf, which then enables a collection of settings (ssp, fortify, and others as they come along) as appropriate to platform and program capability, without having to understand and follow changes in the details of each? Gentoo has a 'hardened' USE flag that many packages take to enable these kinds of mechanisms, and it works well in practice for the user. -- Dan.
Attachment:
pgpsdR9S06yEE.pgp
Description: PGP signature