From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: [gentoo-dev] Debug and strip control, USE flags/$DEBUG
Date: Sat Aug 25 06:03:01 2001 [thread overview]
Message-ID: <200108251205.PAA02471@mailgw2.netvision.net.il> (raw)
Hi all,
The adding of USE flags is currently unregulated, so I thought I'd post to
get a consensus.
Current status: a few ebuilds use env. var. $DEBUG, not explicitly set
anywhere in gentoo config files, to enable debugging. The portage system uses
it to disable automatic binary stripping. The flag is nowhere mentioned in
gentoo docs (AFAIK), a user would have to know about it to enable debugging.
Suggestion: 1. make a $STRIP variable for portage instead. On by default. Set
from make.* so the user can see it.
2. make a USE variable "debug", off by default, for all ebuilds to use.
Note: Right now there are several USE flags which don't have to do with
packages: 3dnow mmx sse build final and maybe some other I missed. Hallski
says adding of USE vars should be regulated somehow, I agree.
Ideas? comments?
--
Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel
next reply other threads:[~2001-08-25 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-25 6:03 Dan Armak [this message]
2001-08-25 6:33 ` [gentoo-dev] Debug and strip control, USE flags/$DEBUG Mikael Hallendal
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=200108251205.PAA02471@mailgw2.netvision.net.il \
--to=danarmak@gentoo.org \
--cc=gentoo-dev@cvs.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