From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-news/rssguard/
Date: Wed, 29 Nov 2017 23:19:54 +0000 (UTC) [thread overview]
Message-ID: <1511997560.6870bf78eaa617688f718773e5181d42ae05f5f5.asturm@gentoo> (raw)
commit: 6870bf78eaa617688f718773e5181d42ae05f5f5
Author: soredake <fdsfgs <AT> krutt <DOT> org>
AuthorDate: Sat Nov 4 14:35:15 2017 +0000
Commit: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Wed Nov 29 23:19:20 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6870bf78
net-news/rssguard: version bump to 3.5.5
| 1 +
| 46 +++++++++++++++++++++++++++++++++
2 files changed, 47 insertions(+)
--git a/net-news/rssguard/Manifest b/net-news/rssguard/Manifest
index 5f0e1692718..2d4bf4d4be2 100644
--- a/net-news/rssguard/Manifest
+++ b/net-news/rssguard/Manifest
@@ -1,2 +1,3 @@
DIST rssguard-3.3.5.tar.gz 5310573 SHA256 c8f9d05d498e63f5654dca2fc27834403d6cd76f078639a5d6e1b2acbc6e81bf SHA512 3d80cffa20f0f5f625907b0245a09ada18d56a190abddf2bcdc9eaa199867e29b68d445e12eec0dc544469e8ead4df2c6753da634346bf60e0913bdae41951be WHIRLPOOL efc16b622f3a0ddccee05c0ff5ba97933b170a8e1b713bf4cd81baeda745e70c88acd34502a372a34df339ab210b929f331609f022be3d5dc88cb9acc74de697
DIST rssguard-3.4.1.tar.gz 5128550 SHA256 709a92daef6cacb53983b42684f1d60eed3b7462a14403a2dac6cdb299a88bd4 SHA512 0f60bc7f1d000ec8e0f813cccf6235602b9a8f25b833b2bbf094601a0bfdeb5a7dfe7a0745f625812c1509b8489c45141fa51206175968897b394f942f4e6e2c WHIRLPOOL 826db0559456988d2b85da1968863ad39cd4f34a21626db27a2c4a45669e4badb07f160c870dfef36b36f03e57fe5efc12db8e1969ed7f17d87f199f6c3af210
+DIST rssguard-3.5.5.tar.gz 6446094 SHA256 fe79a613d983d552c6b1fac155421969c7db5ff27d404cde20ac21c08388f670 SHA512 4e6512c0d58c678145f63a2a42c43abfe4a6ceb8c9d395aba52228ca3afdaaf3dafdd79ab846dada16963f1be5dd22afb877910acc1425aea037d6fa1fc08996 WHIRLPOOL 5bf6b12eb781da34a1589e488a937e50f5857f020c1a5dd9f3e9d03002638c7510959afc3d3f4dae430ee1da73eeba1c6cf4146b362a668624ed5724cefc425c
--git a/net-news/rssguard/rssguard-3.5.5.ebuild b/net-news/rssguard/rssguard-3.5.5.ebuild
new file mode 100644
index 00000000000..ce581c45862
--- /dev/null
+++ b/net-news/rssguard/rssguard-3.5.5.ebuild
@@ -0,0 +1,46 @@
+# Copyright 1999-2017 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=6
+
+inherit flag-o-matic qmake-utils
+
+DESCRIPTION="A tiny RSS and Atom feed reader"
+HOMEPAGE="https://github.com/martinrotter/rssguard"
+SRC_URI="https://github.com/martinrotter/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="GPL-3"
+SLOT="0"
+KEYWORDS="~amd64"
+IUSE="debug webengine"
+MINQT="5.8:5"
+
+RDEPEND="
+ >=dev-qt/qtcore-${MINQT}
+ >=dev-qt/qtgui-${MINQT}
+ >=dev-qt/qtnetwork-${MINQT}
+ >=dev-qt/qtsql-${MINQT}
+ >=dev-qt/qtwidgets-${MINQT}
+ >=dev-qt/qtxml-${MINQT}
+ webengine? ( >=dev-qt/qtwebengine-${MINQT}[widgets] )
+"
+DEPEND="${RDEPEND}
+ >=dev-qt/linguist-tools-${MINQT}
+"
+
+src_configure() {
+ # needed after 8eb640b6f2e140e7c5a1adbe5532cf3662d850b5
+ "$(qt5_get_bindir)/lrelease" rssguard.pro || die "lrelease failed"
+ # CONFIG+=ltcg is needed because of https://github.com/martinrotter/rssguard/issues/156
+ eqmake5 \
+ CONFIG+=$(usex debug debug release) \
+ $(is-flagq -flto* && echo "CONFIG+=ltcg") \
+ USE_WEBENGINE=$(usex webengine true false) \
+ LRELEASE_EXECUTABLE="$(qt5_get_bindir)/lrelease" \
+ PREFIX="${EPREFIX}"/usr \
+ INSTALL_ROOT=.
+}
+
+src_install() {
+ emake install INSTALL_ROOT="${D}"
+}
next reply other threads:[~2017-11-29 23:19 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 23:19 Andreas Sturmlechner [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-12 15:47 [gentoo-commits] repo/gentoo:master commit in: net-news/rssguard/ Michał Górny
2024-10-12 14:57 Sam James
2024-10-07 18:48 Michał Górny
2024-09-27 6:32 Michał Górny
2024-08-10 11:16 Michał Górny
2024-08-10 10:28 Michał Górny
2024-07-26 15:28 Michał Górny
2024-06-15 8:42 Michał Górny
2024-06-15 8:40 Arthur Zamarin
2024-05-31 15:21 Michał Górny
2024-05-31 15:21 Michał Górny
2024-05-30 3:31 Michał Górny
2024-05-15 2:08 Michał Górny
2024-03-30 14:27 Michał Górny
2024-03-30 14:25 Michał Górny
2024-03-15 13:15 Michał Górny
2024-01-18 18:46 Michał Górny
2024-01-18 17:37 Arthur Zamarin
2023-12-15 16:59 Michał Górny
2023-12-09 6:53 Michał Górny
2023-12-07 17:24 Michał Górny
2023-12-02 11:12 Michał Górny
2023-12-02 10:35 Arthur Zamarin
2023-11-14 20:06 Michał Górny
2023-11-13 17:41 Michał Górny
2023-11-12 3:59 Michał Górny
2023-11-11 22:41 Sam James
2023-11-02 14:28 Michał Górny
2023-11-01 16:05 Michał Górny
2023-10-05 14:59 Michał Górny
2023-08-25 9:49 Michał Górny
2023-08-20 10:57 Michał Górny
2023-08-20 10:29 Sam James
2023-07-10 19:26 Arthur Zamarin
2023-06-28 5:06 Michał Górny
2023-05-13 9:04 Michał Górny
2023-05-13 8:40 Arthur Zamarin
2023-05-13 8:35 Michał Górny
2023-05-08 7:44 Joonas Niilola
2023-05-08 7:44 Joonas Niilola
2023-04-04 16:43 Arthur Zamarin
2023-02-09 15:53 Joonas Niilola
2023-02-09 15:53 Joonas Niilola
2023-01-13 13:47 Joonas Niilola
2023-01-13 13:47 Joonas Niilola
2022-10-03 18:34 Ionen Wolkens
2022-06-09 0:57 Ionen Wolkens
2022-03-24 7:28 Ionen Wolkens
2022-01-19 16:28 Joonas Niilola
2021-10-30 6:24 Joonas Niilola
2021-09-28 13:26 Joonas Niilola
2021-09-09 11:30 Joonas Niilola
2021-09-09 11:30 Joonas Niilola
2021-07-07 13:41 Joonas Niilola
2020-12-17 17:33 Sam James
2020-12-16 1:44 Sam James
2020-12-15 3:25 Sam James
2020-12-15 3:25 Sam James
2020-01-18 17:16 Andreas Sturmlechner
2020-01-05 20:08 Jeroen Roovers
2020-01-05 17:00 Andreas Sturmlechner
2020-01-05 17:00 Andreas Sturmlechner
2018-10-20 12:17 Pacho Ramos
2018-10-20 12:17 Pacho Ramos
2018-07-18 21:11 Jonas Stein
2017-11-29 23:19 Andreas Sturmlechner
2017-08-13 13:23 Patrice Clement
2017-08-13 13:23 Patrice Clement
2017-06-20 12:37 Pacho Ramos
2016-11-24 10:54 Michael Palimaka
2015-10-01 14:21 Michael Palimaka
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=1511997560.6870bf78eaa617688f718773e5181d42ae05f5f5.asturm@gentoo \
--to=asturm@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