From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-crypt/tpm2-tools/
Date: Sun, 2 May 2021 16:40:52 +0000 (UTC) [thread overview]
Message-ID: <1619973648.67d70633119f9edce686d0233fded6db1423e8d5.zlogene@gentoo> (raw)
commit: 67d70633119f9edce686d0233fded6db1423e8d5
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sun May 2 16:32:07 2021 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sun May 2 16:40:48 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=67d70633
app-crypt/tpm2-tools: remove libressl support
Package-Manager: Portage-3.0.18, Repoman-3.0.2
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
app-crypt/tpm2-tools/tpm2-tools-4.3.0-r1.ebuild | 8 +++-----
app-crypt/tpm2-tools/tpm2-tools-5.0-r1.ebuild | 8 +++-----
2 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/app-crypt/tpm2-tools/tpm2-tools-4.3.0-r1.ebuild b/app-crypt/tpm2-tools/tpm2-tools-4.3.0-r1.ebuild
index f9edff247c5..01663f80cd5 100644
--- a/app-crypt/tpm2-tools/tpm2-tools-4.3.0-r1.ebuild
+++ b/app-crypt/tpm2-tools/tpm2-tools-4.3.0-r1.ebuild
@@ -12,7 +12,7 @@ SRC_URI="https://github.com/tpm2-software/${PN}/releases/download/${PV}/${P}.tar
LICENSE="BSD"
SLOT="0"
KEYWORDS="~amd64"
-IUSE="+fapi libressl"
+IUSE="+fapi"
# Integration test are now run as part of the testing suite, which will fail
# because none of the supported TPM emulators are in Portage. In a future
@@ -21,13 +21,11 @@ RESTRICT="test"
RDEPEND="net-misc/curl:=
>=app-crypt/tpm2-tss-2.4.0:=[fapi?]
- !libressl? ( dev-libs/openssl:0= )
- libressl? ( dev-libs/libressl:0= )"
+ dev-libs/openssl:0="
DEPEND="${RDEPEND}"
BDEPEND="virtual/pkgconfig
sys-devel/autoconf-archive"
PATCHES=(
- "${FILESDIR}/${PN}-4.3.0-libressl.patch"
"${FILESDIR}/${PN}-4.3.0-Remove-WError.patch"
)
@@ -42,5 +40,5 @@ src_prepare() {
src_configure() {
econf \
$(use_enable fapi) \
- $(use_enable !libressl hardening)
+ --enable-hardening
}
diff --git a/app-crypt/tpm2-tools/tpm2-tools-5.0-r1.ebuild b/app-crypt/tpm2-tools/tpm2-tools-5.0-r1.ebuild
index 375c04e216e..344be726c38 100644
--- a/app-crypt/tpm2-tools/tpm2-tools-5.0-r1.ebuild
+++ b/app-crypt/tpm2-tools/tpm2-tools-5.0-r1.ebuild
@@ -12,7 +12,7 @@ SRC_URI="https://github.com/tpm2-software/${PN}/releases/download/${PV}/${P}.tar
LICENSE="BSD"
SLOT="0"
KEYWORDS="~amd64"
-IUSE="+fapi libressl"
+IUSE="+fapi"
# Integration test are now run as part of the testing suite, which will fail
# because none of the supported TPM emulators are in Portage. In a future
@@ -21,13 +21,11 @@ RESTRICT="test"
RDEPEND="net-misc/curl:=
>=app-crypt/tpm2-tss-3.0.1:=[fapi?]
- !libressl? ( dev-libs/openssl:0= )
- libressl? ( dev-libs/libressl:0= )"
+ dev-libs/openssl:0="
DEPEND="${RDEPEND}"
BDEPEND="virtual/pkgconfig
sys-devel/autoconf-archive"
PATCHES=(
- "${FILESDIR}/${PN}-5.0-libressl.patch"
"${FILESDIR}/${PN}-4.3.0-Remove-WError.patch"
)
@@ -42,5 +40,5 @@ src_prepare() {
src_configure() {
econf \
$(use_enable fapi) \
- $(use_enable !libressl hardening)
+ --enable-hardening
}
next reply other threads:[~2021-05-02 16:40 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 16:40 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-07 6:24 [gentoo-commits] repo/gentoo:master commit in: app-crypt/tpm2-tools/ Sam James
2024-10-02 1:22 Sam James
2024-09-21 19:21 Sam James
2024-07-29 6:22 Joonas Niilola
2024-07-29 6:15 Joonas Niilola
2024-07-29 0:32 Sam James
2024-07-29 0:32 Sam James
2024-07-28 23:58 Jakov Smolić
2024-05-07 10:29 Sam James
2024-05-07 10:29 Sam James
2024-05-07 5:53 Joonas Niilola
2024-05-07 5:53 Joonas Niilola
2024-05-05 11:36 Sam James
2024-05-05 11:36 Sam James
2024-04-16 2:34 Sam James
2024-01-20 13:33 Sam James
2023-09-09 13:17 David Seifert
2023-04-05 20:16 Sam James
2023-04-05 20:16 Sam James
2023-04-05 20:16 Sam James
2023-04-05 20:03 Sam James
2023-04-05 20:03 Sam James
2023-03-15 17:07 Arthur Zamarin
2023-03-15 17:07 Arthur Zamarin
2023-03-15 17:05 Arthur Zamarin
2023-02-20 13:50 Sam James
2023-02-20 13:50 Sam James
2023-02-16 5:08 Sam James
2023-02-16 5:08 Sam James
2023-02-16 5:08 Sam James
2023-02-16 5:08 Sam James
2022-12-21 23:37 Sam James
2022-09-28 0:09 Sam James
2022-09-27 21:44 Sam James
2022-07-15 5:39 Joonas Niilola
2022-07-14 19:37 Arthur Zamarin
2022-07-14 19:37 Arthur Zamarin
2022-07-14 19:37 Arthur Zamarin
2022-07-14 19:37 Arthur Zamarin
2022-04-23 21:34 Sam James
2022-04-23 21:34 Sam James
2022-04-23 21:34 Sam James
2021-12-13 18:28 Arthur Zamarin
2021-12-13 0:06 Sam James
2021-12-13 0:06 Sam James
2021-10-04 14:24 Ionen Wolkens
2021-09-24 7:46 Joonas Niilola
2021-09-24 7:46 Joonas Niilola
2021-09-08 6:46 Sam James
2021-09-08 6:46 Sam James
2021-07-15 2:23 Ionen Wolkens
2021-07-14 6:25 Joonas Niilola
2021-06-21 22:44 Sam James
2021-06-21 22:44 Sam James
2021-06-21 22:44 Sam James
2021-06-21 22:44 Sam James
2021-06-09 6:08 Joonas Niilola
2021-06-09 6:08 Joonas Niilola
2021-04-25 8:00 Michał Górny
2021-01-20 14:13 Joonas Niilola
2021-01-20 14:13 Joonas Niilola
2021-01-20 14:13 Joonas Niilola
2021-01-20 14:13 Joonas Niilola
2020-11-20 11:45 Joonas Niilola
2020-10-08 6:57 Joonas Niilola
2020-08-23 11:48 David Seifert
2020-02-26 16:17 Joonas Niilola
2019-05-30 23:46 Alon Bar-Lev
2018-12-30 21:00 Alon Bar-Lev
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=1619973648.67d70633119f9edce686d0233fded6db1423e8d5.zlogene@gentoo \
--to=zlogene@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