From: "Guilherme Amadio" <amadio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/lcov/
Date: Tue, 6 Mar 2018 14:43:17 +0000 (UTC) [thread overview]
Message-ID: <1520347383.1b2f58a768e8189b9e1b8eb76a3423288d8768c9.amadio@gentoo> (raw)
commit: 1b2f58a768e8189b9e1b8eb76a3423288d8768c9
Author: Guilherme Amadio <amadio <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 6 10:43:52 2018 +0000
Commit: Guilherme Amadio <amadio <AT> gentoo <DOT> org>
CommitDate: Tue Mar 6 14:43:03 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1b2f58a7
dev-util/lcov: prefix support
Package-Manager: Portage-2.3.24, Repoman-2.3.6
dev-util/lcov/lcov-1.13-r1.ebuild | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/dev-util/lcov/lcov-1.13-r1.ebuild b/dev-util/lcov/lcov-1.13-r1.ebuild
index 94b261fb04b..687e3ec26ce 100644
--- a/dev-util/lcov/lcov-1.13-r1.ebuild
+++ b/dev-util/lcov/lcov-1.13-r1.ebuild
@@ -3,6 +3,8 @@
EAPI=6
+inherit prefix
+
DESCRIPTION="A graphical front-end for GCC's coverage testing tool gcov"
HOMEPAGE="http://ltp.sourceforge.net/coverage/lcov.php"
SRC_URI="mirror://sourceforge/ltp/${P}.tar.gz"
@@ -15,6 +17,13 @@ RDEPEND="
dev-lang/perl
dev-perl/GD[png]"
+src_prepare() {
+ default
+ if use prefix; then
+ hprefixify bin/*.{pl,sh}
+ fi
+}
+
src_compile() { :; }
src_install() {
next reply other threads:[~2018-03-06 14:43 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 14:43 Guilherme Amadio [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-01 16:44 [gentoo-commits] repo/gentoo:master commit in: dev-util/lcov/ Sam James
2025-05-01 15:56 Sam James
2025-03-30 15:21 Sebastian Pipping
2025-03-14 15:34 Sam James
2025-03-14 8:12 Sam James
2025-01-11 14:42 Jakov Smolić
2025-01-10 4:41 WANG Xuerui
2025-01-10 4:17 Sam James
2025-01-10 4:17 Sam James
2025-01-10 4:17 Sam James
2025-01-09 23:41 Sebastian Pipping
2025-01-08 15:04 Jakov Smolić
2025-01-08 13:27 Jakov Smolić
2025-01-07 19:51 Sam James
2025-01-07 19:30 Arthur Zamarin
2025-01-07 18:54 Sam James
2025-01-07 18:54 Sam James
2025-01-07 18:30 Sam James
2025-01-07 18:30 Sam James
2025-01-07 1:51 Sebastian Pipping
2025-01-07 1:16 Sebastian Pipping
2025-01-06 20:53 Sebastian Pipping
2025-01-06 18:08 Sebastian Pipping
2025-01-06 17:32 Sebastian Pipping
2024-05-01 8:44 Sam James
2024-01-25 13:44 Sam James
2023-10-14 1:38 Sam James
2023-10-12 5:34 Sam James
2023-10-12 5:28 Sam James
2023-10-12 5:28 Sam James
2021-11-19 8:34 Sam James
2021-08-29 8:37 Marek Szuba
2020-09-29 6:37 Joonas Niilola
2020-09-29 6:37 Joonas Niilola
2020-05-01 8:40 Mart Raudsepp
2019-11-27 1:12 Zac Medico
2019-11-14 0:47 Aaron Bauman
2019-07-18 7:45 Michał Górny
2019-05-22 5:49 Aaron Bauman
2019-03-25 23:18 Patrick McLean
2018-10-22 20:07 Michał Górny
2018-10-22 20:07 Michał Górny
2018-10-22 20:07 Michał Górny
2018-10-22 20:07 Michał Górny
2018-10-22 20:07 Michał Górny
2018-04-18 7:01 Mart Raudsepp
2018-03-28 20:55 Matt Turner
2018-03-01 18:43 Michał Górny
2018-02-11 10:53 Michał Górny
2017-07-19 16:31 Patrice Clement
2017-07-19 15:51 Patrice Clement
2017-05-06 2:05 Michael Orlitzky
2017-05-01 22:34 Sebastian Pipping
2017-02-02 12:26 Manuel Rüger
2017-02-02 12:26 Manuel Rüger
2017-01-14 13:26 Jeroen Roovers
2017-01-06 13:32 Tobias Klausmann
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=1520347383.1b2f58a768e8189b9e1b8eb76a3423288d8768c9.amadio@gentoo \
--to=amadio@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