From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: dev-cpp/wangle/
Date: Sun, 17 Apr 2022 18:13:01 +0000 (UTC) [thread overview]
Message-ID: <1650134627.ee233c0c291450f0ff85a3536c371d89c04da229.arthurzam@gentoo> (raw)
commit: ee233c0c291450f0ff85a3536c371d89c04da229
Author: Alessandro Barbieri <lssndrbarbieri <AT> gmail <DOT> com>
AuthorDate: Sat Apr 16 18:43:47 2022 +0000
Commit: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Apr 16 18:43:47 2022 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=ee233c0c
dev-cpp/wangle: add 2022.04.11.00, drop 2022.03.21.00
Signed-off-by: Alessandro Barbieri <lssndrbarbieri <AT> gmail.com>
dev-cpp/wangle/Manifest | 2 +-
.../{wangle-2022.03.21.00.ebuild => wangle-2022.04.11.00.ebuild} | 6 +++++-
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/dev-cpp/wangle/Manifest b/dev-cpp/wangle/Manifest
index 0b0c9d87b..9c1db0819 100644
--- a/dev-cpp/wangle/Manifest
+++ b/dev-cpp/wangle/Manifest
@@ -1 +1 @@
-DIST wangle-2022.03.21.00.tar.gz 355164 BLAKE2B 876863bb5d0e5c7fd5f3408f9f2233b1995ef838b165bbb9f8772667e1ca5fa98f4ae5eb686e2ef94198bdb373daa2ce96720253f550a808369b8cca0ec6d10b SHA512 069fe7758ccb2f33665f53109047f2e0158e248fda8c760eddd978afd6980acbc6421db60721bf320deca557369377c8757f13c67f8685e3a98394324e75e72e
+DIST wangle-2022.04.11.00.tar.gz 355228 BLAKE2B 1a86d03b0b6518a1b83d59d88ec5fd5f3a2265f951e2d1415e090b6dbdf92842f4726f7aef7e52ed4cb5923ff319051405cf9ef5ecf7eb4db19cce4d54471bff SHA512 8c908f5efcf8315f6779c2a5c5ac0a8de7a9257f661e35b72f6a9e33fe840056c56e1234fc0fc87224f68022b79080ca5360c256d426e5672f2aa2d5e2479371
diff --git a/dev-cpp/wangle/wangle-2022.03.21.00.ebuild b/dev-cpp/wangle/wangle-2022.04.11.00.ebuild
similarity index 81%
rename from dev-cpp/wangle/wangle-2022.03.21.00.ebuild
rename to dev-cpp/wangle/wangle-2022.04.11.00.ebuild
index 1fe53a582..2fa00be7d 100644
--- a/dev-cpp/wangle/wangle-2022.03.21.00.ebuild
+++ b/dev-cpp/wangle/wangle-2022.04.11.00.ebuild
@@ -1,4 +1,4 @@
-# Copyright 2021 Gentoo Authors
+# Copyright 2021-2022 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=8
@@ -12,6 +12,7 @@ SRC_URI="https://github.com/facebook/wangle/archive/v${PV}.tar.gz -> ${P}.tar.gz
LICENSE="Apache-2.0"
SLOT="0"
KEYWORDS="~amd64"
+IUSE="examples test"
RDEPEND="
~dev-cpp/fizz-${PV}:=
@@ -28,10 +29,13 @@ DEPEND="
dev-cpp/gtest
"
+RESTRICT="!test? ( test )"
CMAKE_USE_DIR="${S}/wangle"
src_configure() {
local mycmakeargs=(
+ -DBUILD_EXAMPLES=$(usex examples)
+ -DBUILD_TESTS=$(usex test)
-DLIB_INSTALL_DIR=$(get_libdir)
)
next reply other threads:[~2022-04-17 18:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 18:13 Arthur Zamarin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-15 16:06 [gentoo-commits] repo/proj/guru:master commit in: dev-cpp/wangle/ Julien Roy
2022-03-07 21:21 Ronny Gutbrod
2021-10-28 20:56 Haelwenn Monnier
2021-10-27 6:18 Florian Schmaus
2021-10-25 11:56 Andrew Ammerlaan
2021-10-25 11:56 Andrew Ammerlaan
2021-10-06 1:13 Theo Anderson
2021-07-05 15:48 Haelwenn Monnier
2021-06-17 5:55 Theo Anderson
2021-05-28 10:28 Andrew Ammerlaan
2021-04-29 8:23 Michał Górny
2021-04-29 8:23 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=1650134627.ee233c0c291450f0ff85a3536c371d89c04da229.arthurzam@gentoo \
--to=arthurzam@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