From: "Andreas Sturmlechner" <asturm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/zulucrypt/
Date: Thu, 18 May 2023 12:17:30 +0000 (UTC) [thread overview]
Message-ID: <1684411751.0abceaa4e15fa7af1fc3daaab42a5b59c2fe4e2b.asturm@gentoo> (raw)
commit: 0abceaa4e15fa7af1fc3daaab42a5b59c2fe4e2b
Author: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
AuthorDate: Sun May 14 12:42:49 2023 +0000
Commit: Andreas Sturmlechner <asturm <AT> gentoo <DOT> org>
CommitDate: Thu May 18 12:09:11 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0abceaa4
app-crypt/zulucrypt: Rename USE=gnome -> keyring
Signed-off-by: Andreas Sturmlechner <asturm <AT> gentoo.org>
app-crypt/zulucrypt/metadata.xml | 3 ---
app-crypt/zulucrypt/zulucrypt-5.5.0_pre20180223.ebuild | 8 ++++----
2 files changed, 4 insertions(+), 7 deletions(-)
diff --git a/app-crypt/zulucrypt/metadata.xml b/app-crypt/zulucrypt/metadata.xml
index 91676ea4813e..61d20bbc00aa 100644
--- a/app-crypt/zulucrypt/metadata.xml
+++ b/app-crypt/zulucrypt/metadata.xml
@@ -3,9 +3,6 @@
<pkgmetadata>
<!-- maintainer-needed -->
<use>
- <flag name="gnome">
- Enable support for the freedesktop.org Secret Service API via <pkg>app-crypt/libsecret</pkg>
- </flag>
<flag name="kwallet">
Enable encrypted storage of passwords with <pkg>kde-frameworks/kwallet</pkg>
</flag>
diff --git a/app-crypt/zulucrypt/zulucrypt-5.5.0_pre20180223.ebuild b/app-crypt/zulucrypt/zulucrypt-5.5.0_pre20180223.ebuild
index c037845c99d6..cf3c4dd206ba 100644
--- a/app-crypt/zulucrypt/zulucrypt-5.5.0_pre20180223.ebuild
+++ b/app-crypt/zulucrypt/zulucrypt-5.5.0_pre20180223.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2020 Gentoo Authors
+# Copyright 1999-2023 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=7
@@ -13,13 +13,13 @@ SRC_URI="https://github.com/mhogomchungu/zuluCrypt/archive/${EGIT_COMMIT}.tar.gz
LICENSE="GPL-2+"
SLOT="0"
KEYWORDS="~amd64 ~x86"
-IUSE="gnome kwallet +qt5 udev"
+IUSE="keyring kwallet +qt5 udev"
REQUIRED_USE="kwallet? ( qt5 )"
DEPEND="
dev-libs/libgcrypt:0=
sys-fs/cryptsetup:=
- gnome? ( app-crypt/libsecret )
+ keyring? ( app-crypt/libsecret )
qt5? (
dev-libs/libpwquality
dev-qt/qtcore:5
@@ -39,7 +39,7 @@ PATCHES=( "${FILESDIR}"/${P}-fno-common.patch )
src_configure() {
local mycmakeargs=(
-DLIB_SUFFIX="$(get_libdir)"
- -DNOGNOME=$(usex !gnome)
+ -DNOGNOME=$(usex !keyring)
-DNOKDE=$(usex !kwallet)
-DNOGUI=$(usex !qt5)
-DQT5=true
next reply other threads:[~2023-05-18 12:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 12:17 Andreas Sturmlechner [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-07 21:05 [gentoo-commits] repo/gentoo:master commit in: app-crypt/zulucrypt/ Andreas Sturmlechner
2023-09-04 21:24 Andreas Sturmlechner
2020-12-28 12:43 David Seifert
2020-09-03 10:08 Joonas Niilola
2018-07-19 9:01 Johannes Huber
2018-07-18 21:11 Jonas Stein
2018-04-02 21:20 Patrice Clement
2017-02-25 19:42 [gentoo-commits] repo/gentoo:master commit in: app-crypt/zuluCrypt/ Andreas Sturmlechner
2017-02-02 11:40 Michael Palimaka
2017-01-25 23:29 Patrice Clement
2016-07-07 18:39 Austin English
2016-04-20 3:21 Michał Górny
2015-09-05 23:36 Julian Ospald
2015-08-10 23:47 Julian Ospald
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=1684411751.0abceaa4e15fa7af1fc3daaab42a5b59c2fe4e2b.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