From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:prefix commit in: pym/portage/package/ebuild/
Date: Tue, 4 Feb 2014 20:29:25 +0000 (UTC) [thread overview]
Message-ID: <1391545689.9e892c77acd73757e539548346672217ab8bd976.grobian@gentoo> (raw)
commit: 9e892c77acd73757e539548346672217ab8bd976
Author: Ruud Koolen <redlizard <AT> gentoo <DOT> org>
AuthorDate: Tue Feb 4 20:28:09 2014 +0000
Commit: Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Tue Feb 4 20:28:09 2014 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=9e892c77
doebuild_environment: don't set EPREFIX
`mysettings` is a config object, which initializes a value of EPREFIX in
its constructor (pym/portage/package/ebuild/config.py:489), and it is
this value that should be used, not the constant one.
---
pym/portage/package/ebuild/doebuild.py | 1 -
1 file changed, 1 deletion(-)
diff --git a/pym/portage/package/ebuild/doebuild.py b/pym/portage/package/ebuild/doebuild.py
index 374cc9a..2f08593 100644
--- a/pym/portage/package/ebuild/doebuild.py
+++ b/pym/portage/package/ebuild/doebuild.py
@@ -319,7 +319,6 @@ def doebuild_environment(myebuild, mydo, myroot=None, settings=None,
# due to how it's coded... Don't overwrite this so we can use it.
mysettings["PORTAGE_DEBUG"] = "1"
- mysettings["EPREFIX"] = EPREFIX
mysettings["EBUILD"] = ebuild_path
mysettings["O"] = pkg_dir
mysettings.configdict["pkg"]["CATEGORY"] = cat
next reply other threads:[~2014-02-04 20:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 20:29 Fabian Groffen [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-25 19:32 [gentoo-commits] proj/portage:prefix commit in: pym/portage/package/ebuild/ Fabian Groffen
2015-06-09 19:53 Fabian Groffen
2015-06-09 19:53 Fabian Groffen
2013-12-15 7:56 Fabian Groffen
2012-02-09 8:16 Fabian Groffen
2011-12-23 11:04 Fabian Groffen
2011-12-23 11:04 Fabian Groffen
2011-12-10 12:55 Fabian Groffen
2011-12-02 20:27 Fabian Groffen
2011-02-05 12:25 Fabian Groffen
2011-02-05 12:25 Fabian Groffen
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=1391545689.9e892c77acd73757e539548346672217ab8bd976.grobian@gentoo \
--to=grobian@gentoo.org \
--cc=gentoo-commits@lists.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