public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stefan Strogin" <steils@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/libressl:master commit in: app-crypt/qca/
Date: Fri,  7 Feb 2020 08:55:19 +0000 (UTC)	[thread overview]
Message-ID: <1581065609.ca50ec49c022566889fc7d4aed77e60a4f68da77.steils@gentoo> (raw)

commit:     ca50ec49c022566889fc7d4aed77e60a4f68da77
Author:     Stefan Strogin <steils <AT> gentoo <DOT> org>
AuthorDate: Fri Feb  7 08:53:29 2020 +0000
Commit:     Stefan Strogin <steils <AT> gentoo <DOT> org>
CommitDate: Fri Feb  7 08:53:29 2020 +0000
URL:        https://gitweb.gentoo.org/repo/proj/libressl.git/commit/?id=ca50ec49

app-crypt/qca: sync; 2.2.1 stable for amd64, arm64, x86

Package-Manager: Portage-2.3.87, Repoman-2.3.20
Signed-off-by: Stefan Strogin <steils <AT> gentoo.org>

 app-crypt/qca/qca-2.2.1.ebuild | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/app-crypt/qca/qca-2.2.1.ebuild b/app-crypt/qca/qca-2.2.1.ebuild
index dcb155a..48cd52e 100644
--- a/app-crypt/qca/qca-2.2.1.ebuild
+++ b/app-crypt/qca/qca-2.2.1.ebuild
@@ -1,9 +1,9 @@
-# Copyright 1999-2019 Gentoo Authors
+# Copyright 1999-2020 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=7
 
-inherit cmake-utils qmake-utils
+inherit cmake qmake-utils
 
 DESCRIPTION="Qt Cryptographic Architecture (QCA)"
 HOMEPAGE="https://userbase.kde.org/QCA"
@@ -11,9 +11,10 @@ SRC_URI="mirror://kde/stable/${PN}/${PV}/${P}.tar.xz"
 
 LICENSE="LGPL-2.1"
 SLOT="2"
-KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ppc ~ppc64 ~sparc ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~sparc-solaris"
+KEYWORDS="amd64 ~arm arm64 ~hppa ~ppc ~ppc64 ~sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~sparc-solaris"
 
 IUSE="botan debug doc examples gcrypt gpg libressl logger nss pkcs11 sasl softstore +ssl test"
+RESTRICT="!test? ( test )"
 
 BDEPEND="
 	doc? ( app-doc/doxygen )
@@ -66,16 +67,16 @@ src_configure() {
 		$(qca_plugin_use ssl ossl)
 		-DBUILD_TESTS=$(usex test)
 	)
-	cmake-utils_src_configure
+	cmake_src_configure
 }
 
 src_test() {
 	local -x QCA_PLUGIN_PATH="${BUILD_DIR}/lib/qca"
-	cmake-utils_src_test
+	cmake_src_test
 }
 
 src_install() {
-	cmake-utils_src_install
+	cmake_src_install
 
 	if use doc; then
 		pushd "${BUILD_DIR}" >/dev/null || die


             reply	other threads:[~2020-02-07  8:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07  8:55 Stefan Strogin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-13 14:11 [gentoo-commits] repo/proj/libressl:master commit in: app-crypt/qca/ orbea
2025-04-02  0:01 orbea
2024-10-17  1:22 orbea
2024-07-15  0:59 orbea
2024-07-15  0:59 orbea
2024-03-09 18:48 orbea
2024-02-25  2:42 orbea
2024-01-14 21:44 orbea
2024-01-14 21:44 orbea
2023-08-06 21:40 orbea
2023-08-03 17:38 orbea
2023-06-28  1:12 orbea
2023-06-21 16:17 orbea
2023-06-14 14:41 orbea
2023-05-31 15:34 orbea
2023-05-30 13:12 orbea
2023-05-10 21:14 orbea
2023-04-12 20:24 orbea
2022-12-01 18:19 Quentin Retornaz
2020-07-08  6:06 Stefan Strogin
2020-02-07  8:55 Stefan Strogin
2019-05-05  5:11 Stefan Strogin

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=1581065609.ca50ec49c022566889fc7d4aed77e60a4f68da77.steils@gentoo \
    --to=steils@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