public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <warnera6@egr.msu.edu>
To: gentoo-dev@lists.gentoo.org, funtoos@yahoo.com, warnera6@egr.msu.edu
Subject: [gentoo-dev] The dreaded debug use flag/eclass
Date: Mon, 01 Aug 2005 21:22:15 -0400	[thread overview]
Message-ID: <42EECAC7.6010907@egr.msu.edu> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Oh yeah, it's back, for the 6th time :)

I've provided links to all the other discussions I could find on
theaimsgroup in case you want to take a trip down memory lane.
Hopefully I'll summarize the previous discussion well enough that you
don't have to torture yourself..too much.

The latest discussion ( [4], [5] ) was brought up by SpanKY about how
the debug use flag and eclass are used differently depending on the
situation.  Some used the flag for turning on internal debugging
routines ( think verbose library output ).  Some used the flag to change
 CFLAGS and turn off stripping so that the debug symbols would remain
intact.

- From use.desc we gather:
skyfw@kyoto /usr/portage/profiles $ cat use.desc | grep debug
debug - Tells configure and the makefiles to build for debugging.
Effects vary across packages, but generally it will at least add -g to
CFLAGS. Remember to set FEATURES=nostrip too

Many people do not like the fact that a USE flag changes CFLAGS.
Although there are other USE flags that do this too ( pic comes to mind
in a couple ebuilds, checkpassword fex ) they are a minority compared to
debug.  People want to be able to debug things in a simple manner, and
this is not easily possible with the current portage system.  It
requires per-package FEATURES ( which is bottled with a host of other
things, see [6] ).

So, for future versions of portage ( not stable, unless per-package
features makes it in...somehow ) we add a FEATURE called "debug".  This
FEATURE will:
1. Set CFLAGS to a gentoo standard set ( perhaps user configurable ) of
flags.
2. Will turn on FEATURES="nostrip".
3. Anything else it should do? ( Redhat's moving debug info to a
seperate location perhaps? [3]

The debug.eclass will be depreciated.  The DEBUG use flag will change
names to an agreed upon name that specifies the addition of debuging
output.  Foser's debuginfo change seemed appropriately named ( although
thanks for changing it back :) ).

No more eclass, no more packages inheriting from the debug but not even
using the USE flag, just one per-package feature.

[1] http://marc.theaimsgroup.com/?l=gentoo-dev&w=2&r=8&s=debug&q=b
[2] http://marc.theaimsgroup.com/?l=gentoo-dev&w=2&r=7&s=debug&q=b
[3] http://marc.theaimsgroup.com/?l=gentoo-dev&w=2&r=4&s=debug&q=b
[4] http://marc.theaimsgroup.com/?l=gentoo-dev&w=2&r=2&s=debug&q=b
[5] http://marc.theaimsgroup.com/?l=gentoo-dev&w=2&r=1&s=debug&q=b
[6] http://bugs.gentoo.org/show_bug.cgi?id=44796
[7] http://bugs.gentoo.org/show_bug.cgi?id=55708
[8] http://bugs.gentoo.org/show_bug.cgi?id=55977

- -Alec Warner ( Antarus )
warnera6@egr.msu.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBQu7KxmzglR5RwbyYAQIXjg//VjprL1CML8ZfYvSNLI/AujugOs1p3M4X
zFomIdqklIlzYNYet6qKe8esi3TQe59/UwYvQBTsIg7gXYI3ij6oq81CbU7MQUY5
DK1YKlAdsW75EKwhc8Bo47m7X9medC55m6XcoiweRPoEcsF9B1Aw1qfRm5B9WT8J
hYtRmp0vHvdF9Viw0t5ekpX3VvYrqffheClUs9i0VraDikZ3ycKk8cKGpxPDUxE1
CwcnaPMN2HKNNW2jieH4rrTVRNCaZ2ZIf/x5QlaU1i8W20KzoT5JUAkMQVcsQtby
FTfN35xgK1BFGblPHpb4taRGgwa2oaQwXUV+aux8nZy9jYXPBQcEXFRSoGKpHlNp
uAftITo93MDC06PqcstVBCsJJTTiiP6MGIyfn+U0ghopPBpF7/Cn9RLQxrTbBJVC
M2yEIZ+mb+3Nneii5kUe9ErH2EgEt/K2UkPLNXZBS6kiFI9AGSQZK/3bVE3QUbFM
hN5hP0IGgS7WU3qFO8PluOOoIm/uDhG9XyWoCqW0rO5rLv2eCeqpNhIhZANs2Plw
xjZuGnPkMLA1TxF2OZoc5T3+/gUHX/2Y/aAItYTZra+lvQBEZMXz3Kxoz4vmWjWs
rWsbTejZMUUUfd8XVXxBLw4WFt2V2pDdla1LzAx9lF+aSMm15NhdwmfCV7nHblaU
bB+LTL4QH9g=
=3iaR
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list



             reply	other threads:[~2005-08-02  1:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-02  1:22 Alec Warner [this message]
2005-08-02  2:07 ` [gentoo-dev] The dreaded debug use flag/eclass Mike Frysinger
2005-08-02  2:26   ` Mike Frysinger
2005-08-02  2:43     ` Danny van Dyk
2005-08-02  2:52       ` Mike Frysinger
2005-08-02 11:10         ` Danny van Dyk
2005-08-02 13:22       ` Mike Frysinger
2005-08-03 11:16         ` Martin Schlemmer
2005-08-03 12:50           ` Mike Frysinger
2005-08-03 13:11             ` Danny van Dyk
2005-08-24 11:13               ` Paul de Vrieze
2005-08-02 15:38   ` Alec Warner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42EECAC7.6010907@egr.msu.edu \
    --to=warnera6@egr.msu.edu \
    --cc=funtoos@yahoo.com \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox