From: Ned Ludd <solar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] fix binary debug support, part elevenity billion + 1
Date: Wed, 07 Jun 2006 17:55:21 -0400 [thread overview]
Message-ID: <1149717321.25264.4.camel@localhost> (raw)
In-Reply-To: <4487319D.1000103@gentoo.org>
On Wed, 2006-06-07 at 16:05 -0400, Alec Warner wrote:
> We've discussed this multiple times, and it's always been the conclusion
> that per package.env should go in bashrc, as bashrc is generally more
> powerful than anything we could devise. The only downside afaik, for
> bashrc is that you can't do per package FEATURES as FEATURES is a
> python-side var. But you shouldn't need per package FEATURES by design;
> FEATURES are for portage, not your ebuild.
This is a thumbs up? I've got the code sitting in my
$PORTDIR/profiles/base/profile.bashrc to give us just this.
I'd be all to happy to commit it. So that's a yes right? :)
--
Ned Ludd <solar@gentoo.org>
Gentoo Linux
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-07 21:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 15:13 [gentoo-dev] fix binary debug support, part elevenity billion + 1 Brian Harring
2006-06-07 16:24 ` Mike Frysinger
2006-06-07 18:30 ` Zac Medico
2006-06-07 19:31 ` Grant Goodyear
2006-06-07 20:05 ` Alec Warner
2006-06-07 20:30 ` Zac Medico
2006-06-07 21:15 ` Graham Murray
2006-06-07 21:55 ` Ned Ludd [this message]
2006-06-07 23:12 ` Alec Warner
2006-06-08 10:07 ` Mike Frysinger
2006-06-08 10:49 ` Alec Warner
2006-06-08 13:16 ` Kevin F. Quinn
2006-06-08 13:24 ` Ned Ludd
2006-06-08 13:41 ` Alec Warner
2006-06-08 14:06 ` Ned Ludd
2006-06-08 14:49 ` Donnie Berkholz
2006-06-08 15:47 ` Ned Ludd
2006-06-08 16:54 ` Donnie Berkholz
2006-06-29 22:14 ` Ned Ludd
2006-06-07 20:10 ` Zac Medico
2006-06-08 10:10 ` Mike Frysinger
2006-06-08 11:37 ` Zac Medico
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=1149717321.25264.4.camel@localhost \
--to=solar@gentoo.org \
--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