From: "Kent Fredric" <kentnl@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Crypt-OpenSSL-RSA/
Date: Wed, 1 Jul 2020 18:02:08 +0000 (UTC) [thread overview]
Message-ID: <1593626507.8d41955622b8a53542702f5be2de27692b98eee1.kentnl@gentoo> (raw)
commit: 8d41955622b8a53542702f5be2de27692b98eee1
Author: Kent Fredric <kentnl <AT> gentoo <DOT> org>
AuthorDate: Wed Jul 1 18:01:25 2020 +0000
Commit: Kent Fredric <kentnl <AT> gentoo <DOT> org>
CommitDate: Wed Jul 1 18:01:47 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8d419556
dev-perl/Crypt-OpenSSL-RSA: Bump to version 0.310.0
- EAPI7
- Cleanup DESCRIPTION
- Always prune bad tests
- Parallel testing
- Ensure CFLAGS pass through to compiler via make
Upstream:
- Fix compat with OpenSSL 1.1.0
- Prefer hash mode NID_sha256 over NID_sha1 for sign
- Use Crypt::OpenSSL::Guess to find openssl stuff
- Use new interface for RSA_generate_key when possible
- Add fixes to work with LibreSSL better
- Remove default of SHA256 for RSA keys
Keywording:
- Due to new dependency dev-perl/Crypt-OpenSSL-Guess, the following
keywords were dropped:
alpha amd64-linux arm{,64} hppa ia64 m68k{,-mint} mips
ppc{,-aix,-macos,64} s390 sparc{,-solaris,64-solaris}
x64-{macos,solaris} x86-{linux,macos,solaris}
Package-Manager: Portage-2.3.100, Repoman-2.3.22
Signed-off-by: Kent Fredric <kentnl <AT> gentoo.org>
.../Crypt-OpenSSL-RSA-0.310.0.ebuild | 48 ++++++++++++++++++++++
dev-perl/Crypt-OpenSSL-RSA/Manifest | 1 +
2 files changed, 49 insertions(+)
diff --git a/dev-perl/Crypt-OpenSSL-RSA/Crypt-OpenSSL-RSA-0.310.0.ebuild b/dev-perl/Crypt-OpenSSL-RSA/Crypt-OpenSSL-RSA-0.310.0.ebuild
new file mode 100644
index 00000000000..87892490f35
--- /dev/null
+++ b/dev-perl/Crypt-OpenSSL-RSA/Crypt-OpenSSL-RSA-0.310.0.ebuild
@@ -0,0 +1,48 @@
+# Copyright 1999-2020 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+DIST_AUTHOR=TODDR
+DIST_VERSION=0.31
+inherit perl-module
+
+DESCRIPTION="RSA encoding and decoding using the OpenSSL libraries"
+
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+IUSE="libressl test"
+RESTRICT="!test? ( test )"
+
+RDEPEND="
+ dev-perl/Crypt-OpenSSL-Bignum
+ dev-perl/Crypt-OpenSSL-Random
+ !libressl? ( dev-libs/openssl:0= )
+ libressl? ( dev-libs/libressl:= )
+"
+DEPEND="
+ !libressl? ( dev-libs/openssl:0= )
+ libressl? ( dev-libs/libressl:= )
+"
+BDEPEND="${RDEPEND}
+ >=dev-perl/Crypt-OpenSSL-Guess-0.110.0
+ virtual/perl-ExtUtils-MakeMaker
+ test? (
+ virtual/perl-Test
+ )
+"
+PERL_RM_FILES=(
+ t/z_kwalitee.t
+ t/z_perl_minimum_version.t
+ t/z_meta.t
+ t/z_pod-coverage.t
+ t/z_pod.t
+)
+mydoc="rfc*.txt"
+
+src_compile() {
+ mymake=(
+ "OPTIMIZE=${CFLAGS}"
+ )
+ perl-module_src_compile
+}
diff --git a/dev-perl/Crypt-OpenSSL-RSA/Manifest b/dev-perl/Crypt-OpenSSL-RSA/Manifest
index 98a8cec936c..8e5e142b707 100644
--- a/dev-perl/Crypt-OpenSSL-RSA/Manifest
+++ b/dev-perl/Crypt-OpenSSL-RSA/Manifest
@@ -1 +1,2 @@
DIST Crypt-OpenSSL-RSA-0.28.tar.gz 20035 BLAKE2B 9b98a22e68f2c16a38c0aee6ee9a509cd6c6b1d20b1c6533856b7682aa074c24a2e12e87ebdaf3deb7011cbe257737335646b52be74537533d836cbf6fb6ce6d SHA512 4a20c3f814e80ea15304b2a189001172e72237d703a0f9281e7e46d593c521508abfac3a259701994ec867f160821bec37e4e8234d04b792168db19b065ce324
+DIST Crypt-OpenSSL-RSA-0.31.tar.gz 25856 BLAKE2B 172d48cd6cc0f3df2c1c1684897d8ee376663cb366a1e28c13e4af603b2b985d542f83284112be5e4717a3a13a512926b4413b5a8f08f7ed613cd9929683cce9 SHA512 e00d25fc1d39253ea2d7d6ee478403d2b38bd9125602baf5815672fb9e81674ff58bbb47539e425526db1988ebc1a40837372cf42ffd466cb532efa2e450ccab
next reply other threads:[~2020-07-01 18:02 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 18:02 Kent Fredric [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-12 5:00 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Crypt-OpenSSL-RSA/ Sam James
2025-07-12 3:11 Sam James
2025-07-12 2:56 Sam James
2025-06-06 3:44 Sam James
2022-12-24 7:11 Sam James
2022-11-16 23:18 Sam James
2022-11-16 7:58 Arthur Zamarin
2022-11-15 10:04 Sam James
2022-11-15 10:04 Sam James
2022-11-15 8:46 Sam James
2022-11-15 8:46 Sam James
2022-11-15 8:46 Sam James
2022-11-15 8:46 Sam James
2022-07-09 5:57 Sam James
2021-12-05 20:36 Arthur Zamarin
2021-12-05 3:15 Sam James
2021-12-05 3:15 Sam James
2021-12-05 3:11 Sam James
2021-12-05 3:09 Sam James
2021-12-05 3:08 Sam James
2021-10-16 10:43 Andreas K. Hüttel
2021-10-16 10:43 Andreas K. Hüttel
2021-05-15 18:02 Sam James
2021-05-15 2:37 Sam James
2021-05-14 9:36 Agostino Sarubbo
2021-05-14 9:35 Agostino Sarubbo
2021-05-14 9:32 Agostino Sarubbo
2021-05-14 9:31 Agostino Sarubbo
2021-05-14 6:40 Agostino Sarubbo
2021-05-03 10:21 Mikle Kolyada
2020-12-05 4:20 Kent Fredric
2020-11-28 9:57 Sam James
2020-10-22 5:11 Joshua Kinard
2020-09-26 19:44 Matt Turner
2020-09-03 4:26 Yixun Lan
2020-07-12 0:10 Sam James
2020-07-10 11:16 Sam James
2020-07-09 13:23 Sam James
2020-07-07 6:58 Sergei Trofimovich
2020-07-06 16:43 Sergei Trofimovich
2020-07-05 11:37 Sergei Trofimovich
2020-07-05 11:35 Sergei Trofimovich
2020-07-04 8:56 Sergei Trofimovich
2019-07-29 18:42 Aaron Bauman
2019-04-01 19:33 Andreas Sturmlechner
2018-10-27 12:31 Fabian Groffen
2018-08-18 5:29 Mikle Kolyada
2018-06-13 16:21 Lars Wendler
2016-08-16 5:05 Kent Fredric
2015-12-30 23:04 Andreas Hüttel
2015-09-20 16:39 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=1593626507.8d41955622b8a53542702f5be2de27692b98eee1.kentnl@gentoo \
--to=kentnl@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