From: "Andrew Savchenko" <bircoph@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/oprofile/
Date: Mon, 7 Aug 2017 15:24:25 +0000 (UTC) [thread overview]
Message-ID: <1502119458.160721afa4c8412a31aec830469b7389d0210616.bircoph@gentoo> (raw)
commit: 160721afa4c8412a31aec830469b7389d0210616
Author: Andrew Savchenko <bircoph <AT> gentoo <DOT> org>
AuthorDate: Mon Aug 7 15:21:45 2017 +0000
Commit: Andrew Savchenko <bircoph <AT> gentoo <DOT> org>
CommitDate: Mon Aug 7 15:24:18 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=160721af
dev-util/oprofile: remove the kludge for java-pkg-opt-2.eclass
java-pkg-opt-2.eclass is now fixed in the tree, the kludge is no
longer needed.
Package-Manager: Portage-2.3.6, Repoman-2.3.3
Signed-off-by: Andrew Savchenko <bircoph <AT> gentoo.org>
dev-util/oprofile/oprofile-1.2.0.ebuild | 6 ------
1 file changed, 6 deletions(-)
diff --git a/dev-util/oprofile/oprofile-1.2.0.ebuild b/dev-util/oprofile/oprofile-1.2.0.ebuild
index 066d0a54020..c548ac8146e 100644
--- a/dev-util/oprofile/oprofile-1.2.0.ebuild
+++ b/dev-util/oprofile/oprofile-1.2.0.ebuild
@@ -39,12 +39,6 @@ pkg_setup() {
use java && java-pkg_init
}
-# kludge for the bug in java-pkg-opt-2.eclass
-# https://archives.gentoo.org/gentoo-dev/message/2b8c7f0ed39423050a763418ca884ed7
-src_prepare() {
- use java && java-pkg-opt-2_src_prepare || eapply_user
-}
-
src_configure() {
econf \
--disable-werror \
next reply other threads:[~2017-08-07 15:24 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 15:24 Andrew Savchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-10 6:47 [gentoo-commits] repo/gentoo:master commit in: dev-util/oprofile/ Miroslav Šulc
2022-11-24 3:25 Mike Gilbert
2021-07-23 19:57 Conrad Kostecki
2021-07-22 19:28 Conrad Kostecki
2021-07-22 19:28 Conrad Kostecki
2021-05-04 7:03 Agostino Sarubbo
2021-05-03 16:53 Sam James
2021-05-02 13:29 Andrew Savchenko
2020-12-02 23:21 Sam James
2020-08-30 13:05 Andrew Savchenko
2019-07-14 13:46 Andrew Savchenko
2019-06-13 19:17 Markus Meier
2019-05-26 7:31 Sergei Trofimovich
2019-05-13 0:38 Thomas Deutschmann
2019-05-07 8:46 Tobias Klausmann
2019-04-19 1:32 Aaron Bauman
2018-12-19 22:48 Sergei Trofimovich
2018-12-08 12:14 Mikle Kolyada
2018-11-28 20:14 Tobias Klausmann
2018-10-30 13:21 Mikle Kolyada
2018-10-28 21:29 Thomas Deutschmann
2018-10-27 20:08 Andrew Savchenko
2017-12-10 9:27 Ulrich Müller
2017-09-14 22:01 Sven Wegener
2017-08-23 6:42 Andrew Savchenko
2017-08-23 6:42 Andrew Savchenko
2017-07-30 11:55 Andrew Savchenko
2016-12-25 22:45 Andrew Savchenko
2016-12-25 10:23 Agostino Sarubbo
2016-12-25 10:23 Agostino Sarubbo
2016-12-25 10:09 Agostino Sarubbo
2016-12-25 10:09 Agostino Sarubbo
2016-12-24 10:18 Agostino Sarubbo
2016-12-24 10:18 Agostino Sarubbo
2016-11-22 17:10 Andrew Savchenko
2016-06-02 19:10 Tobias Klausmann
2016-06-02 18:58 Tobias Klausmann
2016-05-25 5:59 Jeroen Roovers
2016-05-25 5:59 Jeroen Roovers
2016-05-25 5:47 Jeroen Roovers
2016-05-25 5:30 Jeroen Roovers
2016-04-19 19:33 Markus Meier
2016-04-05 11:56 Jeroen Roovers
2016-04-01 19:10 Markus Meier
2016-03-22 14:32 Agostino Sarubbo
2016-03-19 16:32 Agostino Sarubbo
2015-09-29 19:49 Andrew Savchenko
2015-09-29 19:49 Andrew Savchenko
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=1502119458.160721afa4c8412a31aec830469b7389d0210616.bircoph@gentoo \
--to=bircoph@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