From: "Jeroen Roovers" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-office/calcurse/
Date: Mon, 25 Jun 2018 13:31:26 +0000 (UTC) [thread overview]
Message-ID: <1529933484.bbb7be5ae6a19863dd23089ea19351d94c4a913e.jer@gentoo> (raw)
commit: bbb7be5ae6a19863dd23089ea19351d94c4a913e
Author: Jeroen Roovers <jer <AT> gentoo <DOT> org>
AuthorDate: Mon Jun 25 13:31:10 2018 +0000
Commit: Jeroen Roovers <jer <AT> gentoo <DOT> org>
CommitDate: Mon Jun 25 13:31:24 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bbb7be5a
app-office/calcurse: Again sys-libs/ncurses[tinfo] (bug #529804).
Package-Manager: Portage-2.3.40, Repoman-2.3.9
app-office/calcurse/calcurse-4.3.0.ebuild | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/app-office/calcurse/calcurse-4.3.0.ebuild b/app-office/calcurse/calcurse-4.3.0.ebuild
index a7a63942ebd..e772e98c93f 100644
--- a/app-office/calcurse/calcurse-4.3.0.ebuild
+++ b/app-office/calcurse/calcurse-4.3.0.ebuild
@@ -3,7 +3,7 @@
EAPI=6
-inherit eutils multilib-minimal
+inherit autotools eutils multilib-minimal
DESCRIPTION="a text-based calendar and scheduling application"
HOMEPAGE="https://calcurse.org/"
@@ -18,10 +18,18 @@ RDEPEND="
DEPEND="
${RDEPEND}"
+PATCHES=(
+ "${FILESDIR}"/${PN}-4.2.1-tinfo.patch
+)
# Most tests fail.
RESTRICT="test"
+src_prepare() {
+ default
+ eautoreconf
+}
+
multilib_src_configure() {
ECONF_SOURCE="${S}" econf
}
next reply other threads:[~2018-06-25 13:31 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 13:31 Jeroen Roovers [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-28 15:23 [gentoo-commits] repo/gentoo:master commit in: app-office/calcurse/ Sam James
2025-03-28 15:10 Sam James
2025-03-28 15:10 Sam James
2024-07-17 13:24 Arthur Zamarin
2024-07-17 9:50 Arthur Zamarin
2024-07-17 9:50 Arthur Zamarin
2024-06-06 19:56 Hanno Böck
2023-07-07 21:57 Conrad Kostecki
2023-05-30 6:59 Joonas Niilola
2023-05-30 6:59 Joonas Niilola
2023-05-30 6:59 Joonas Niilola
2023-05-02 20:11 Sam James
2023-05-02 19:32 Arthur Zamarin
2023-05-02 19:24 Sam James
2023-05-02 19:06 Arthur Zamarin
2023-03-22 8:08 Viorel Munteanu
2023-02-08 17:13 Sam James
2022-10-14 5:06 Arthur Zamarin
2021-12-05 18:39 Sam James
2021-12-05 18:31 Sam James
2021-12-05 4:16 Sam James
2021-01-07 19:37 Sam James
2021-01-07 11:15 Sam James
2021-01-04 3:31 Sam James
2020-11-04 15:13 Joonas Niilola
2020-11-04 15:13 Joonas Niilola
2020-03-12 20:49 Mike Gilbert
2020-03-12 20:49 Mike Gilbert
2020-03-12 20:49 Mike Gilbert
2020-03-11 8:24 Patrice Clement
2020-03-10 15:07 Andreas K. Hüttel
2020-03-10 11:28 Patrice Clement
2019-05-20 11:14 Mikle Kolyada
2019-05-12 22:03 Sergei Trofimovich
2019-05-12 21:57 Sergei Trofimovich
2019-02-25 21:54 Patrice Clement
2019-02-25 21:54 Patrice Clement
2018-08-26 14:49 Patrice Clement
2018-08-25 21:27 Patrice Clement
2018-06-24 14:51 Patrice Clement
2018-06-24 14:51 Patrice Clement
2018-06-03 13:49 Aaron Bauman
2017-11-14 21:51 Patrice Clement
2017-02-24 13:38 Agostino Sarubbo
2017-02-24 9:01 Michael Weber
2017-02-08 22:15 Patrice Clement
2016-01-19 14:21 Patrice Clement
2016-01-19 13:33 Patrice Clement
2015-10-24 9:03 Patrice Clement
2015-10-24 9:03 Patrice Clement
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=1529933484.bbb7be5ae6a19863dd23089ea19351d94c4a913e.jer@gentoo \
--to=jer@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