From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:prefix commit in: pym/portage/
Date: Fri, 9 Dec 2011 20:39:29 +0000 (UTC) [thread overview]
Message-ID: <1d0a2f6f5415e45c7de297927b175d5f58b94e24.grobian@gentoo> (raw)
commit: 1d0a2f6f5415e45c7de297927b175d5f58b94e24
Author: Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Fri Dec 9 20:39:21 2011 +0000
Commit: Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Fri Dec 9 20:39:21 2011 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=1d0a2f6f
const.py: rely on EPREFIX from const_autotool.py
---
pym/portage/const.py | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/pym/portage/const.py b/pym/portage/const.py
index 336c005..83d6696 100644
--- a/pym/portage/const.py
+++ b/pym/portage/const.py
@@ -191,7 +191,9 @@ MANIFEST2_IDENTIFIERS = ("AUX", "MISC", "DIST", "EBUILD")
# a config instance (since it's possible to contruct a config instance with
# a different EPREFIX). Therefore, the EPREFIX constant should *NOT* be used
# in the definition of any other contstants within this file.
-EPREFIX=""
+# PREFIX LOCAL: rely on EPREFIX from autotools
+#EPREFIX=""
+# END PREFIX LOCAL
# pick up EPREFIX from the environment if set
if "__PORTAGE_TEST_EPREFIX" in os.environ:
next reply other threads:[~2011-12-09 20:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 20:39 Fabian Groffen [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-10 12:06 [gentoo-commits] proj/portage:prefix commit in: pym/portage/ Fabian Groffen
2011-12-10 12:12 Fabian Groffen
2011-12-10 12:55 Fabian Groffen
2011-12-14 15:29 Fabian Groffen
2012-01-18 7:58 Fabian Groffen
2012-03-01 20:32 Fabian Groffen
2012-09-30 11:10 Fabian Groffen
2012-09-30 11:10 Fabian Groffen
2012-10-02 11:59 Fabian Groffen
2013-01-27 21:51 Fabian Groffen
2017-12-12 8:13 Fabian Groffen
2018-05-18 19:46 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=1d0a2f6f5415e45c7de297927b175d5f58b94e24.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