From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-patches:master commit in: /
Date: Sat, 15 Feb 2020 19:59:53 +0000 (UTC) [thread overview]
Message-ID: <1581796761.511a79b9e1266603fdebbeb15287627d9240db2c.slyfox@gentoo> (raw)
commit: 511a79b9e1266603fdebbeb15287627d9240db2c
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Feb 15 19:59:21 2020 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Feb 15 19:59:21 2020 +0000
URL: https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=511a79b9
make-tarball.sh: tweak scrip to work on non-empty EPREFIX
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
make-tarball.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/make-tarball.sh b/make-tarball.sh
index 082da40..a626a3d 100755
--- a/make-tarball.sh
+++ b/make-tarball.sh
@@ -9,7 +9,7 @@ ver=${1%/}
for ebuild in \
${ver} \
/usr/local/src/gentoo/repo/gentoo/sys-devel/gcc/gcc-${ver}.ebuild \
- "$(portageq get_repo_path / gentoo)"/sys-devel/gcc/gcc-${ver}.ebuild \
+ "$(portageq get_repo_path $(portageq envvar EPREFIX)/ gentoo)"/sys-devel/gcc/gcc-${ver}.ebuild \
/usr/portage/sys-devel/gcc/gcc-${ver}.ebuild \
""
do
next reply other threads:[~2020-02-15 19:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 19:59 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-27 16:23 [gentoo-commits] proj/gcc-patches:master commit in: / Sam James
2022-08-27 16:23 Sam James
2022-05-22 23:16 Sam James
2022-04-25 1:12 Sam James
2022-04-10 11:37 Sam James
2022-04-10 11:37 Sam James
2022-04-09 3:02 Sam James
2022-01-08 3:49 Sam James
2022-01-08 3:49 Sam James
2022-01-08 3:49 Sam James
2020-12-30 17:26 Sergei Trofimovich
2020-05-28 23:04 Sergei Trofimovich
2018-08-08 7:54 Sergei Trofimovich
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=1581796761.511a79b9e1266603fdebbeb15287627d9240db2c.slyfox@gentoo \
--to=slyfox@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