From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:prefix commit in: bin/
Date: Thu, 28 Jul 2022 18:33:23 +0000 (UTC) [thread overview]
Message-ID: <1659033082.7aeca65f71a37d00d2c73d5ba5f583da014c0dec.grobian@gentoo> (raw)
commit: 7aeca65f71a37d00d2c73d5ba5f583da014c0dec
Author: Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Thu Jul 28 18:31:22 2022 +0000
Commit: Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Thu Jul 28 18:31:22 2022 +0000
URL: https://gitweb.gentoo.org/proj/portage.git/commit/?id=7aeca65f
bin/phase-functions.sh: drop Prefix announce
I can't seem to figure out how to trigger this function at all, which
means, if it is possible to trigger afterall (not via ebuild command),
it will be via an obscure route that doesn't really matter whether or
not EPREFIX value is advertised.
Signed-off-by: Fabian Groffen <grobian <AT> gentoo.org>
bin/phase-functions.sh | 4 ----
1 file changed, 4 deletions(-)
diff --git a/bin/phase-functions.sh b/bin/phase-functions.sh
index 212b19fc1..8efd12f22 100644
--- a/bin/phase-functions.sh
+++ b/bin/phase-functions.sh
@@ -771,10 +771,6 @@ __dyn_help() {
echo "production (stripped)"
fi
echo " merge to : ${ROOT}"
- # PREFIX LOCAL: identify
- if [[ -n "${EPREFIX}" ]]; then
- echo " offset : ${EPREFIX}"
- fi
echo
if [[ -n "$USE" ]]; then
echo "Additionally, support for the following optional features will be enabled:"
next reply other threads:[~2022-07-28 18:33 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 18:33 Fabian Groffen [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-03 20:19 [gentoo-commits] proj/portage:prefix commit in: bin/ Sam James
2022-08-16 17:04 Fabian Groffen
2022-07-28 18:23 Fabian Groffen
2022-07-25 16:55 Fabian Groffen
2022-07-25 16:49 Fabian Groffen
2021-07-06 7:10 Fabian Groffen
2021-01-04 10:42 Fabian Groffen
2020-12-07 16:49 Fabian Groffen
2020-11-28 19:47 Fabian Groffen
2020-11-28 19:37 Fabian Groffen
2019-07-01 13:11 Fabian Groffen
2019-06-03 19:21 Fabian Groffen
2019-06-03 19:00 Fabian Groffen
2018-12-23 19:55 Fabian Groffen
2018-12-06 12:46 Fabian Groffen
2017-03-24 7:43 Fabian Groffen
2017-03-23 15:25 Fabian Groffen
2014-10-24 19:14 Fabian Groffen
2014-10-02 18:47 Fabian Groffen
2014-09-30 16:04 Fabian Groffen
2013-10-06 19:01 Fabian Groffen
2013-09-18 18:34 Fabian Groffen
2013-09-18 18:34 Fabian Groffen
2013-09-12 7:32 Fabian Groffen
2013-08-16 12:50 Fabian Groffen
2013-03-31 10:03 Fabian Groffen
2013-03-24 8:45 Fabian Groffen
2013-03-24 8:34 Fabian Groffen
2013-01-10 21:13 Fabian Groffen
2012-12-26 15:06 Fabian Groffen
2012-12-02 12:58 Fabian Groffen
2012-10-22 17:57 Fabian Groffen
2012-09-30 12:12 Fabian Groffen
2012-09-12 18:26 Fabian Groffen
2012-08-12 7:44 Fabian Groffen
2012-07-08 17:25 Fabian Groffen
2012-04-03 18:09 Fabian Groffen
2011-12-10 13:14 Fabian Groffen
2011-12-09 20:36 Fabian Groffen
2011-12-03 16:49 Fabian Groffen
2011-12-03 15:22 Fabian Groffen
2011-09-23 18:33 Fabian Groffen
2011-09-23 18:23 Fabian Groffen
2011-09-13 18:45 Fabian Groffen
2011-08-20 18:35 Fabian Groffen
2011-04-24 17:20 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=1659033082.7aeca65f71a37d00d2c73d5ba5f583da014c0dec.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