From: "James Le Cuirot" <chewi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-java/java-config/
Date: Thu, 18 Feb 2016 19:13:18 +0000 (UTC) [thread overview]
Message-ID: <1455822793.1a6ccc8cf7cea82ab69307af3966184380113e6c.chewi@gentoo> (raw)
commit: 1a6ccc8cf7cea82ab69307af3966184380113e6c
Author: James Le Cuirot <chewi <AT> gentoo <DOT> org>
AuthorDate: Thu Feb 18 19:12:38 2016 +0000
Commit: James Le Cuirot <chewi <AT> gentoo <DOT> org>
CommitDate: Thu Feb 18 19:13:13 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1a6ccc8c
dev-java/java-config: Deal with java-config-wrapper the right way
I'm a dumbass. 'nuff said.
Package-Manager: portage-2.2.27
.../{java-config-2.2.0-r1.ebuild => java-config-2.2.0-r2.ebuild} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-java/java-config/java-config-2.2.0-r1.ebuild b/dev-java/java-config/java-config-2.2.0-r2.ebuild
similarity index 93%
rename from dev-java/java-config/java-config-2.2.0-r1.ebuild
rename to dev-java/java-config/java-config-2.2.0-r2.ebuild
index 171c3ed..75780b7 100644
--- a/dev-java/java-config/java-config-2.2.0-r1.ebuild
+++ b/dev-java/java-config/java-config-2.2.0-r2.ebuild
@@ -28,7 +28,7 @@ python_install_all() {
distutils-r1_python_install_all
# This replaces the file installed by java-config-wrapper.
- cp -a "${ED}/usr/bin/${PN}-2" "${ED}/usr/bin/${PN}" || die
+ dosym java-config-2 /usr/bin/java-config
}
python_test() {
next reply other threads:[~2016-02-18 19:13 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 19:13 James Le Cuirot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-08 6:28 [gentoo-commits] repo/gentoo:master commit in: dev-java/java-config/ Sam James
2024-07-29 8:55 Arthur Zamarin
2024-07-27 11:58 Sam James
2024-07-27 11:58 Sam James
2024-07-27 11:58 Sam James
2024-06-27 7:23 Florian Schmaus
2023-12-20 15:47 Michał Górny
2023-12-20 10:36 Sam James
2023-12-20 10:36 Sam James
2023-12-20 10:36 Sam James
2023-11-17 8:25 Florian Schmaus
2023-11-16 20:30 Florian Schmaus
2023-11-16 15:55 Florian Schmaus
2023-11-14 14:12 Florian Schmaus
2023-11-14 14:11 Florian Schmaus
2023-11-14 14:11 Florian Schmaus
2023-10-12 9:47 Sam James
2023-09-17 14:35 Arthur Zamarin
2023-05-30 18:01 Mike Gilbert
2023-01-03 13:01 Florian Schmaus
2022-05-01 20:47 Georgy Yakovlev
2021-12-25 10:11 Georgy Yakovlev
2021-05-23 9:10 Miroslav Šulc
2021-05-23 9:08 Miroslav Šulc
2021-05-23 9:08 Miroslav Šulc
2020-12-15 19:32 Fabian Groffen
2020-11-05 22:41 Patrice Clement
2020-07-16 21:10 Patrice Clement
2020-07-09 11:52 Sam James
2020-07-05 13:44 Agostino Sarubbo
2020-07-05 13:36 Agostino Sarubbo
2020-07-05 8:52 Sergei Trofimovich
2020-06-23 13:30 Patrice Clement
2020-06-23 13:30 Patrice Clement
2020-06-18 7:36 Patrice Clement
2020-06-17 21:04 Patrice Clement
2020-04-29 18:31 Thomas Deutschmann
2020-04-18 3:02 Craig Andrews
2020-04-15 5:54 Mike Gilbert
2019-05-18 10:02 Michał Górny
2019-01-05 23:17 Georgy Yakovlev
2018-11-02 21:37 Patrice Clement
2017-05-05 15:28 Manuel Rüger
2017-01-24 20:21 James Le Cuirot
2016-04-03 22:36 James Le Cuirot
2016-04-03 22:36 James Le Cuirot
2016-02-21 11:55 James Le Cuirot
2016-02-18 17:05 James Le Cuirot
2015-09-11 7:53 Justin Lecher
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=1455822793.1a6ccc8cf7cea82ab69307af3966184380113e6c.chewi@gentoo \
--to=chewi@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