Jason Stubbs wrote:
On Saturday 08 January 2005 16:41, Mike Frysinger wrote:
On Saturday 08 January 2005 02:24 am, Jason Stubbs wrote:
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.
everytime i suggest a FEATURE no one likes it :)
Since when has people's likes and dislikes ever bothered you? ;)
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.
that may be, but in order for the debug eclass to work, ebuilds have to
inherit it ...
Therefore, why not have debugging included
in the default CFLAGS and have the stages and GRP built with those?
debug eclass also disables stripping ... and it only does stuff if you have
USE=debug, meaning it doesnt affect GRP / default users at all
Heh.. I'm not saying the debug eclass is good; I think it is terrible. I'm
suggesting that the CFLAGS be something like "-march=foo -O2 -g" and that
FEATURES include "nostrip" by default, including the stages and GRP. From a
support point of view, it should make things a lot easier.
Regards,
Jason Stubbs
--
[email protected] mailing list
Part of me is torn here. Having debuging enabled on GRP and stages
sounds like a great idea in theory. I guess the deal is how much the
users are going to complain when they find out that all their programs
are built with debugging symbols? Granted it's not a problem for me
personally because I build from stage1 all the time, so I'll gladly
remove the FEATURE, but some people are installing gentoo on small
drives. How much extra space does debugging info take up on a system,
or on the LiveCD?
--
Alec Warner
Spartasoft Secretary ( spartasoft.msu.edu )
Junior Computer Science
Michigan State University
[EMAIL PROTECTED]
--
[email protected] mailing list
