On Sun, Jan 12, 2014 at 01:53:47AM -0600, Ryan Hill wrote: > While I'm adding USE defaults to toolchain.eclass and moving them out of the > profiles, I thought now would be a good time to review a couple default flag > settings. > > mudflap: > This is currently enabled by default but I'd like to disable it. It controls > libmudflap and the -fmudflap flag. I think the only reason this flag exists > is > so we can disable it in crossdev. It's not required by anything in the tree, > the code is bitrotten and has been removed for GCC 4.9. If you know how to use > -fmudflap, you know how to set a USE flag.
No-brainer, yeah. > fortran: > Do we want to keep enabling fortran by default? The majority of users will > never get the urge to install a fortran package, and the fortran eclass > handles > those that do. I think it should be treated as all the other optional > languages and disabled by default, but I'd like to know if there are other > opinions. Yes, keep it. It's used in the oddest places, and still beats C for numeric processing. It's not like gcj which is a pig to build, and to which there are many alternative implementations that may well be preferred, given the state of Java. IMO it's important to have, and there's no real benefit to keeping it off, for the general user. Anyone who wants to keep it slim already has it disabled in package.use. -- #friendly-coders -- We're friendly, but we're not /that/ friendly ;-)
