From: "Conrad Kostecki" <conikost@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-im/libcommuni/
Date: Sat, 11 Jul 2020 12:02:17 +0000 (UTC) [thread overview]
Message-ID: <1594468850.82b84eccdbb760daaf7b50df02241b3b75295d51.conikost@gentoo> (raw)
commit: 82b84eccdbb760daaf7b50df02241b3b75295d51
Author: Conrad Kostecki <conikost <AT> gentoo <DOT> org>
AuthorDate: Sat Jul 11 12:00:26 2020 +0000
Commit: Conrad Kostecki <conikost <AT> gentoo <DOT> org>
CommitDate: Sat Jul 11 12:00:50 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=82b84ecc
net-im/libcommuni: bump to newest snapshot
As bonus all tests can be now enabled.
Package-Manager: Portage-2.3.103, Repoman-2.3.23
Signed-off-by: Conrad Kostecki <conikost <AT> gentoo.org>
net-im/libcommuni/Manifest | 1 +
.../libcommuni/libcommuni-3.5.0_p20200711.ebuild | 79 ++++++++++++++++++++++
2 files changed, 80 insertions(+)
diff --git a/net-im/libcommuni/Manifest b/net-im/libcommuni/Manifest
index e249fb6d677..35e9aa558c2 100644
--- a/net-im/libcommuni/Manifest
+++ b/net-im/libcommuni/Manifest
@@ -1 +1,2 @@
DIST libcommuni-3.5.0_p20190110.tar.gz 471278 BLAKE2B 2836a5ae01b08aac624c899a40712a9c452fc5b8f242906063936e48bd59306758cc70ea07beaf8488d228d6029c8128e343bbd59b1bfeff9bb2dccda0153b59 SHA512 9da065ef6b0589f7406d8c66b46f9f8d3d16325b59b7281153233b1a8d2bf98cdd35ee4e416237ac760dfc07531578aa7432226932976b9bbf36209bed5db72c
+DIST libcommuni-3.5.0_p20200711.tar.gz 471839 BLAKE2B 37a02c473496a0fe9394a8b019678afa96b07b9272556fd538d42d9ec296b34ad4c76b3110ff96732bccbed59f2faeedf80bd7782e7a6e395252c6430cb88fa7 SHA512 578e2f70bdfa0e62eb3acac4e8deb2f6f0c1cd5f0a5e559dae79d2a808b27d3cf63ede146a65026e156d988097a5b7903793acadcd7e9ac567f65c59e6738ed3
diff --git a/net-im/libcommuni/libcommuni-3.5.0_p20200711.ebuild b/net-im/libcommuni/libcommuni-3.5.0_p20200711.ebuild
new file mode 100644
index 00000000000..b65aeca5172
--- /dev/null
+++ b/net-im/libcommuni/libcommuni-3.5.0_p20200711.ebuild
@@ -0,0 +1,79 @@
+# Copyright 1999-2020 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+EGIT_COMMIT="85fc0d9d8659269b00499975d184d75e67f63a9f"
+
+inherit qmake-utils
+
+DESCRIPTION="A cross-platform IRC framework written with Qt"
+HOMEPAGE="https://communi.github.io/"
+SRC_URI="https://github.com/communi/${PN}/archive/${EGIT_COMMIT}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="BSD"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+IUSE="examples qml test +uchardet"
+RESTRICT="!test? ( test )"
+
+RDEPEND="
+ dev-qt/qtcore:5
+ dev-qt/qtdeclarative:5
+ examples? ( || (
+ dev-qt/qtgui:5[X(-)]
+ dev-qt/qtgui:5[xcb(-)]
+ ) )
+ uchardet? ( app-i18n/uchardet )
+ !uchardet? ( dev-libs/icu:= )
+"
+
+DEPEND="
+ ${RDEPEND}
+ test? ( dev-qt/qttest:5 )
+"
+
+S="${WORKDIR}/${PN}-${EGIT_COMMIT}"
+
+src_configure() {
+ local myqmakeargs=( libcommuni.pro
+ # Disables compile run-time benchmarks, as they don't make any sense
+ -config no_benchmarks
+ # Is needed for fixing the QA Notice: The following files contain insecure RUNPATHs
+ -config no_rpath
+ # Compile libcommuni always in Release mode, as Debug seems to do nothing
+ -config release
+ # Don't silence all compile messages
+ -config verbose
+ -config $(usex examples '' 'no_')examples
+ -config $(usex qml '' 'no_')qml
+ -config $(usex test '' 'no_')tests
+ -config $(usex uchardet 'no_' '')icu
+ -config $(usex uchardet '' 'no_')uchardet )
+
+ eqmake5 "${myqmakeargs[@]}"
+}
+
+src_test() {
+ # This is a hack to delete the existing LD_LIBRARY_PATH and set a new one,
+ # otherwise a test will fail, because it uses the system installed lib instead of the new compiled lib.
+ # The test will fail, when libcommuni is emerged with USE="uchardet" and
+ # libcommuni is already installed with USE="-uchardat", or the other way around.
+ find "${S}" -type f -name 'target_wrapper.sh' -exec sed -i -e "/.*LD_LIBRARY_PATH.*/d" {} \; || die
+ local -x LD_LIBRARY_PATH="${S}/lib"
+
+ default
+}
+
+src_install() {
+ emake install INSTALL_ROOT="${D}"
+
+ if use examples; then
+ local examples=( "bot" "client" "minimal" "qmlbot" "quick" )
+ for example in ${examples[@]}; do
+ newbin examples/"${example}"/"${example}" libcommuni."${example}"
+ done
+ fi
+
+ einstalldocs
+}
next reply other threads:[~2020-07-11 12:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-11 12:02 Conrad Kostecki [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-08 23:21 [gentoo-commits] repo/gentoo:master commit in: net-im/libcommuni/ Conrad Kostecki
2025-03-08 23:21 Conrad Kostecki
2025-03-08 23:21 Conrad Kostecki
2024-07-21 15:02 Conrad Kostecki
2022-03-12 11:52 Conrad Kostecki
2022-03-12 11:52 Conrad Kostecki
2022-03-12 11:52 Conrad Kostecki
2021-02-02 21:27 Conrad Kostecki
2021-02-02 21:27 Conrad Kostecki
2021-02-02 21:27 Conrad Kostecki
2021-01-03 20:52 Conrad Kostecki
2020-08-11 18:30 Conrad Kostecki
2020-08-11 14:23 Agostino Sarubbo
2020-08-10 12:04 Agostino Sarubbo
2020-01-19 23:53 Andreas Sturmlechner
2020-01-19 23:53 Andreas Sturmlechner
2019-12-17 15:59 Conrad Kostecki
2019-12-16 7:49 Agostino Sarubbo
2019-12-15 13:43 Agostino Sarubbo
2019-12-03 0:02 Conrad Kostecki
2019-09-24 3:40 Joonas Niilola
2019-04-13 19:10 Agostino Sarubbo
2018-11-03 21:58 Michał Górny
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=1594468850.82b84eccdbb760daaf7b50df02241b3b75295d51.conikost@gentoo \
--to=conikost@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