public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kent Fredric" <kentnl@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Crypt-SMIME/
Date: Thu,  2 Jul 2020 13:10:08 +0000 (UTC)	[thread overview]
Message-ID: <1593695396.5b09ea03e77c4f12e23b930b97ae125097bbe1ba.kentnl@gentoo> (raw)

commit:     5b09ea03e77c4f12e23b930b97ae125097bbe1ba
Author:     Kent Fredric <kentnl <AT> gentoo <DOT> org>
AuthorDate: Thu Jul  2 13:09:34 2020 +0000
Commit:     Kent Fredric <kentnl <AT> gentoo <DOT> org>
CommitDate: Thu Jul  2 13:09:56 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5b09ea03

dev-perl/Crypt-SMIME: -r bump for EAPI7 and CFLAGS love

- EAPI7
- Unconditionally patch bad tests
- Ensure CFLAGS passed through make/compiler

Package-Manager: Portage-2.3.100, Repoman-2.3.22
Signed-off-by: Kent Fredric <kentnl <AT> gentoo.org>

 dev-perl/Crypt-SMIME/Crypt-SMIME-0.250.0-r1.ebuild | 49 ++++++++++++++++++++++
 1 file changed, 49 insertions(+)

diff --git a/dev-perl/Crypt-SMIME/Crypt-SMIME-0.250.0-r1.ebuild b/dev-perl/Crypt-SMIME/Crypt-SMIME-0.250.0-r1.ebuild
new file mode 100644
index 00000000000..f7a56171e9d
--- /dev/null
+++ b/dev-perl/Crypt-SMIME/Crypt-SMIME-0.250.0-r1.ebuild
@@ -0,0 +1,49 @@
+# Copyright 1999-2020 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+DIST_AUTHOR=MIKAGE
+DIST_VERSION=0.25
+inherit perl-module
+
+DESCRIPTION="S/MIME message signing, verification, encryption and decryption"
+
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+IUSE="libressl test minimal"
+RESTRICT="!test? ( test )"
+
+RDEPEND="
+	!libressl? ( >=dev-libs/openssl-0.9.9:0 )
+	libressl? ( dev-libs/libressl )
+	virtual/perl-XSLoader
+"
+BDEPEND="${RDEPEND}
+	virtual/perl-ExtUtils-MakeMaker
+	dev-perl/ExtUtils-PkgConfig
+	dev-perl/ExtUtils-CChecker
+	>=virtual/perl-ExtUtils-Constant-0.230.0
+	test? (
+		dev-perl/Test-Exception
+		virtual/perl-Test-Simple
+		!minimal? (
+			>=dev-perl/Test-Taint-1.60.0
+			>=dev-perl/Taint-Util-0.80.0
+		)
+	)
+"
+PERL_RM_FILES=(
+	t/boilerplate.t
+	t/manifest.t
+	t/dependencies.t
+	t/pod-coverage.t
+	t/pod.t
+)
+
+src_compile() {
+	mymake=(
+		"OPTIMIZE=${CFLAGS}"
+	)
+	perl-module_src_compile
+}


             reply	other threads:[~2020-07-02 13:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 13:10 Kent Fredric [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-28 12:26 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Crypt-SMIME/ Andreas K. Hüttel
2024-06-09 21:18 Sam James
2024-04-29  4:45 Sam James
2022-12-18 18:50 Arthur Zamarin
2022-11-15  8:46 Sam James
2022-10-31 16:38 Agostino Sarubbo
2021-06-22 18:19 Sam James
2021-05-03 10:25 Mikle Kolyada
2020-10-19  3:58 Kent Fredric
2020-09-17 12:25 Kent Fredric
2020-09-16  8:53 Kent Fredric
2020-08-07 15:47 Kent Fredric
2020-08-06 16:56 Kent Fredric
2016-12-10 18:01 Kent Fredric
2016-12-05 19:35 Kent Fredric
2016-09-05  5:47 Kent Fredric
2016-09-05  5:47 Kent Fredric
2016-01-09 21:20 Andreas Hüttel
2015-12-31 10:46 Andreas Hüttel
2015-12-31 10:46 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=1593695396.5b09ea03e77c4f12e23b930b97ae125097bbe1ba.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