public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
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: Thu, 08 Jun 2006 09:24:33 -0400	[thread overview]
Message-ID: <1149773073.31288.16.camel@onyx> (raw)
In-Reply-To: <448800C3.5080807@gentoo.org>

On Thu, 2006-06-08 at 06:49 -0400, Alec Warner wrote:
> Mike Frysinger wrote:
> > On Wednesday 07 June 2006 19:12, Alec Warner wrote:
> > 
> >>I would be more concerned with convincing the rest of the developers.
> >>adding crap in base profile.bashrc will affect 99% of users, so it
> >>better be friggin correct and useful, otherwise you will piss a ton of
> >>people off.
> > 
> > 
> > versus the people who are really annoyed that such support hasnt yet been 
> > integrated into portage proper ?
> > 
> > yes, from the portage side of things, it may be a pita to implement 
> > per-package env ... but from the user side of things, it's a huge help
> > -mike
> 
> My e-mail was basically worded as to say "Solar paste your crap to this 
> ML." 

Alright...

tail -n 6 /usr/portage/profiles/uclibc/profile.bashrc

#for conf in ${PN}-${PV}-${PR} ${PN}-${PV} ${PN}; do
#       if [[ -r /etc/portage/env/$CATEGORY/${conf} ]]; then
#               . /etc/portage/env/$CATEGORY/${conf}
#               break
#       fi
#done

>  Is there any reason you need package.env in portage proper as 
> opposed to bashrc?

Nope.. bashrc is the only way to access the variables in a way that 
is the most friendly to the bash side of things.

-- 
Ned Ludd <solar@gentoo.org>
Gentoo Linux

-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-06-08 13:29 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
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 [this message]
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=1149773073.31288.16.camel@onyx \
    --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