From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: gnatbuild.eclass
Date: Thu, 11 Oct 2007 23:38:16 -0700 [thread overview]
Message-ID: <20071012063816.GH23990@supernova> (raw)
In-Reply-To: <fen401$lu6$2@sea.gmane.org>
On 07:28 Fri 12 Oct , Steve Long wrote:
> Donnie Berkholz wrote:
>
> > On 18:17 Wed 10 Oct , George Shapovalov (george) wrote:
> >> george 07/10/10 18:17:58
> >>
> >> Modified: gnatbuild.eclass
> >>
> >> Log: fixed src_install issue, no longer relies on portage leaking
> >> env vars between functions
> >
> > It's really sad that you have to add this workaround.
> >
> If it's an env var that needs to be set in different phases, it doesn't
> sound so bad to me? export or setting vars in the global ebuild scope is
> fine imo.
Portage is supposed to preserve the environment across functions. This
workaround is added because that seems to break on a regular basis.
Thanks,
Donnie
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2007-10-12 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Ifg86-0000SO-TD@stork.gentoo.org>
2007-10-10 18:19 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: gnatbuild.eclass Donnie Berkholz
2007-10-12 6:28 ` Steve Long
2007-10-12 6:38 ` Donnie Berkholz [this message]
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=20071012063816.GH23990@supernova \
--to=dberkholz@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