From: "Nicolas Bock" <nicolasbock@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: mail-client/neomutt/
Date: Wed, 6 Jun 2018 12:01:49 +0000 (UTC) [thread overview]
Message-ID: <1528286502.bc106dfb53a99bd56cf0785f2ecd79d0f93db6d9.nicolasbock@gentoo> (raw)
commit: bc106dfb53a99bd56cf0785f2ecd79d0f93db6d9
Author: Nicolas Bock <nicolasbock <AT> gentoo <DOT> org>
AuthorDate: Wed Jun 6 12:00:58 2018 +0000
Commit: Nicolas Bock <nicolasbock <AT> gentoo <DOT> org>
CommitDate: Wed Jun 6 12:01:42 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bc106dfb
mail-client/neomutt: Deprecate old crypt USE flags
Package-Manager: Portage-2.3.40, Repoman-2.3.9
mail-client/neomutt/neomutt-99999999.ebuild | 37 +++++++++--------------------
1 file changed, 11 insertions(+), 26 deletions(-)
diff --git a/mail-client/neomutt/neomutt-99999999.ebuild b/mail-client/neomutt/neomutt-99999999.ebuild
index 6d374739048..fb8ad83183d 100644
--- a/mail-client/neomutt/neomutt-99999999.ebuild
+++ b/mail-client/neomutt/neomutt-99999999.ebuild
@@ -19,9 +19,9 @@ HOMEPAGE="https://neomutt.org/"
LICENSE="GPL-2"
SLOT="0"
-IUSE="berkdb crypt doc gdbm gnutls gpg gpgme idn kerberos kyotocabinet
- libressl lmdb nls notmuch pgp_classic qdbm sasl selinux slang smime
- smime_classic ssl tokyocabinet"
+IUSE="berkdb doc gdbm gnutls gpgme idn kerberos kyotocabinet libressl
+ lmdb nls notmuch pgp_classic qdbm sasl selinux slang smime_classic
+ ssl tokyocabinet"
CDEPEND="
app-misc/mime-types
@@ -40,7 +40,6 @@ CDEPEND="
qdbm? ( dev-db/qdbm )
tokyocabinet? ( dev-db/tokyocabinet )
gnutls? ( >=net-libs/gnutls-1.0.17 )
- gpg? ( >=app-crypt/gpgme-0.9.0 )
gpgme? ( >=app-crypt/gpgme-0.9.0 )
idn? ( net-dns/libidn )
kerberos? ( virtual/krb5 )
@@ -74,14 +73,9 @@ src_configure() {
"$(use_enable nls)"
"$(use_enable notmuch)"
- # During the transition of the crypto USE flags we need to support
- # both sets of flags. We do not want to emit a configuration setting
- # twice, since the second flag overrides the first, potentially
- # leading to unwanted settings. See https://bugs.gentoo.org/640824 for
- # details.
- "$(if use gpg || use gpgme; then echo "--enable"; else echo "--disable"; fi)-gpgme"
- "$(if use crypt || use pgp_classic; then echo "--enable"; else echo "--disable"; fi)-pgp"
- "$(if use smime || use smime_classic; then echo "--enable"; else echo "--disable"; fi)-smime"
+ "$(use_enable gpgme)"
+ "$(use_enable pgp_classic pgp)"
+ "$(use_enable smime_classic smime)"
# Database backends.
"$(use_enable berkdb bdb)"
@@ -127,19 +121,10 @@ src_install() {
}
pkg_postinst() {
- if use crypt || use gpg || use smime; then
- ewarn "Pleae note that the crypto related USE flags of neomutt have changed."
- ewarn "(https://bugs.gentoo.org/637176)"
- ewarn "crypt -> pgp_classic"
- ewarn "gpg -> gpgme"
- ewarn "smime -> smime_classic"
- ewarn "The old USE flags still work but their use is deprecated and will"
- ewarn "be removed in a future release."
- if use gpg && ( use crypt || use smime ); then
- ewarn " Note that gpgme (old gpg) includes both pgp and smime"
- ewarn " support. You can probably remove pgp_classic (old crypt)"
- ewarn " and smime_classic (old smime) from your USE-flags and"
- ewarn " only enable gpgme."
- fi
+ if use gpgme && ( use pgp_classic || use smime_classic ); then
+ ewarn " Note that gpgme (old gpg) includes both pgp and smime"
+ ewarn " support. You can probably remove pgp_classic (old crypt)"
+ ewarn " and smime_classic (old smime) from your USE-flags and"
+ ewarn " only enable gpgme."
fi
}
next reply other threads:[~2018-06-06 12:01 UTC|newest]
Thread overview: 137+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 12:01 Nicolas Bock [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-13 10:23 [gentoo-commits] repo/gentoo:master commit in: mail-client/neomutt/ Marc Schiffbauer
2025-01-09 22:02 Nicolas Bock
2025-01-09 11:09 Marc Schiffbauer
2024-12-13 21:59 Nicolas Bock
2024-12-13 21:54 Nicolas Bock
2024-11-25 19:00 Nicolas Bock
2024-11-25 18:23 Nicolas Bock
2024-11-25 18:17 Nicolas Bock
2024-05-25 6:27 Arthur Zamarin
2024-05-25 6:27 Arthur Zamarin
2024-05-12 23:00 Marc Schiffbauer
2024-05-12 23:00 Marc Schiffbauer
2024-02-19 13:36 Marc Schiffbauer
2023-12-21 17:47 Nicolas Bock
2023-12-21 17:47 Nicolas Bock
2023-11-14 14:40 Nicolas Bock
2023-11-14 14:24 Nicolas Bock
2023-11-14 14:20 Nicolas Bock
2023-11-14 14:19 Nicolas Bock
2023-11-14 4:32 Nicolas Bock
2023-11-03 15:05 Nicolas Bock
2023-10-29 11:33 Marc Schiffbauer
2023-10-28 17:24 Nicolas Bock
2023-05-17 19:01 Nicolas Bock
2023-05-12 17:56 Nicolas Bock
2023-05-12 17:54 Nicolas Bock
2023-05-05 13:47 Nicolas Bock
2023-05-02 20:31 Nicolas Bock
2023-04-27 16:25 Nicolas Bock
2023-04-07 10:07 Sam James
2023-03-23 13:22 Nicolas Bock
2023-03-23 3:42 Sam James
2023-03-22 17:26 Nicolas Bock
2023-03-22 17:26 Nicolas Bock
2023-01-06 20:03 Arthur Zamarin
2023-01-06 20:03 Arthur Zamarin
2022-08-30 8:27 Jakov Smolić
2022-06-16 16:30 Sam James
2022-05-23 19:37 Nicolas Bock
2022-04-29 18:32 Nicolas Bock
2022-04-26 2:27 Sam James
2022-04-15 18:29 Nicolas Bock
2022-04-08 17:04 Nicolas Bock
2022-03-28 6:53 Agostino Sarubbo
2022-03-26 19:47 Agostino Sarubbo
2022-03-26 0:12 Sam James
2022-03-08 22:03 Nicolas Bock
2021-10-29 19:19 Nicolas Bock
2021-10-22 13:42 Nicolas Bock
2021-10-15 17:41 Nicolas Bock
2021-09-28 16:38 Nicolas Bock
2021-05-26 8:09 Thomas Deutschmann
2021-05-25 19:10 Agostino Sarubbo
2021-05-25 18:58 Agostino Sarubbo
2021-05-14 0:22 Sam James
2021-04-30 12:47 Mikle Kolyada
2021-03-10 14:32 Nicolas Bock
2021-02-05 18:58 Nicolas Bock
2021-01-25 23:39 Sam James
2020-12-13 0:16 Sam James
2020-12-03 15:26 Nicolas Bock
2020-12-02 3:06 Thomas Deutschmann
2020-12-01 14:02 Nicolas Bock
2020-12-01 12:10 Sam James
2020-11-30 16:53 Nicolas Bock
2020-11-27 15:34 Nicolas Bock
2020-11-23 17:49 Nicolas Bock
2020-11-22 19:10 Nicolas Bock
2020-11-01 11:18 Georgy Yakovlev
2020-11-01 11:18 Georgy Yakovlev
2020-09-25 14:46 Nicolas Bock
2020-09-25 13:59 Nicolas Bock
2020-08-26 11:45 Nicolas Bock
2020-08-26 11:45 Nicolas Bock
2020-07-29 0:20 Sam James
2020-07-27 22:25 Sam James
2020-07-27 21:15 Sam James
2020-07-27 19:51 Nicolas Bock
2020-07-27 19:51 Nicolas Bock
2020-06-29 14:29 Thomas Deutschmann
2020-06-29 13:25 Nicolas Bock
2020-06-29 13:16 Nicolas Bock
2020-06-19 20:12 Nicolas Bock
2020-05-11 12:53 Nicolas Bock
2020-05-01 23:45 Nicolas Bock
2020-04-26 11:55 Nicolas Bock
2020-04-25 13:22 Nicolas Bock
2020-04-20 11:44 Nicolas Bock
2020-03-20 14:06 Nicolas Bock
2020-03-13 17:15 Nicolas Bock
2020-03-13 17:12 Nicolas Bock
2020-03-13 17:07 Nicolas Bock
2020-03-13 17:04 Nicolas Bock
2019-12-09 13:06 Nicolas Bock
2019-11-29 21:26 Nicolas Bock
2019-11-11 12:38 Nicolas Bock
2019-11-06 5:29 Nicolas Bock
2019-11-06 3:13 Nicolas Bock
2019-11-02 15:04 Thomas Deutschmann
2019-11-02 12:03 Nicolas Bock
2019-10-11 18:15 Nicolas Bock
2019-10-11 12:40 Nicolas Bock
2019-08-11 8:45 Michał Górny
2018-10-07 0:10 Mikle Kolyada
2018-10-06 23:05 Thomas Deutschmann
2018-07-24 17:42 Nicolas Bock
2018-06-23 18:09 Mikle Kolyada
2018-06-22 14:52 Nicolas Bock
2018-06-06 12:02 Nicolas Bock
2018-06-06 11:47 Nicolas Bock
2018-06-06 11:47 Nicolas Bock
2018-06-06 11:47 Nicolas Bock
2018-06-04 15:18 Nicolas Bock
2018-06-03 14:00 Nicolas Bock
2018-04-04 22:17 Nicolas Bock
2018-04-03 13:39 Nicolas Bock
2018-02-23 12:34 Nicolas Bock
2018-02-23 12:34 Nicolas Bock
2018-01-24 21:53 Nicolas Bock
2018-01-24 21:40 Nicolas Bock
2018-01-03 13:07 Nicolas Bock
2017-12-27 13:11 Nicolas Bock
2017-12-15 12:24 Nicolas Bock
2017-12-14 13:56 Nicolas Bock
2017-12-13 15:50 Nicolas Bock
2017-12-09 13:29 Nicolas Bock
2017-12-03 17:39 Nicolas Bock
2017-12-03 16:31 Nicolas Bock
2017-12-03 13:41 Nicolas Bock
2017-12-03 13:41 Nicolas Bock
2017-12-02 14:29 Nicolas Bock
2017-11-20 12:42 Nicolas Bock
2017-11-20 12:22 Nicolas Bock
2017-10-27 15:32 Nicolas Bock
2017-10-13 16:04 Nicolas Bock
2017-10-04 11:41 Nicolas Bock
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=1528286502.bc106dfb53a99bd56cf0785f2ecd79d0f93db6d9.nicolasbock@gentoo \
--to=nicolasbock@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