On Saturday 08 January 2005 14:19, Mike Frysinger wrote:
> so, might we finally settle on this ? here's a solution i think would make
> everyone happy:
> - get rid of debug.elcass (having every single ebuild 'inherit debug' is
> ugly) - USE=debug will force portage to:
> - auto append nostrip to either FEATURES/RESTRICT, doesnt matter
> - export CFLAGS=${CFLAGS_DEBUG:--g -gdb -pipe}
> - export CXXFLAGS=${CXXFLAGS_DEBUG:--g -gdb}
This shouldn't be a USE flag. USE flags should only pertain to ebuilds. If
portage is to do this, it should be a FEATURE.
> - stop using 'debug' in ebuilds unless a package wants to add more crap to
> CFLAGS for debugging purposes
Bad idea in my opinion. It would cause issues similar to what we have now -
ie. no uniformity on what the flag does.
> - create a new USE flag, debuginc, which turns on internal debugging
> routines (the meaning of this of course varies between packages)
The "debug" flag probably should be renamed, regardless of what happens
otherwise, so that users (and developers) have a clear understanding of the
flag.
> - switch to using the existing 'profile' USE flag for profiling generation
If this affects CFLAGS only, I think this is a bad idea too.
As far as I understand it, the debug eclass was created because it's too much
of a bother to explain to users how to turn on debugging information in order
to get useful feedback. Therefore, why not have debugging included in the
default CFLAGS and have the stages and GRP built with those? Those users that
remove them would then know how to reenable them by default. Those users who
don't touch the CFLAGS (a fair proportion nowadays) are able to provide the
required information by default. Is the slight loss in performance the only
reason this isn't done already?
Regards,
Jason Stubbs
--
[email protected] mailing list
