public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Test-Strict/
Date: Wed,  3 Apr 2019 15:46:19 +0000 (UTC)	[thread overview]
Message-ID: <1554306346.bddf0df8a80ed05e196546daafc13b9848069cc9.dilfridge@gentoo> (raw)

commit:     bddf0df8a80ed05e196546daafc13b9848069cc9
Author:     Andreas K. Huettel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Wed Apr  3 15:44:47 2019 +0000
Commit:     Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Wed Apr  3 15:45:46 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bddf0df8

dev-perl/Test-Strict: New package, ebuild by ulm, bug 681918

Closes: https://bugs.gentoo.org/681918
Package-Manager: Portage-2.3.62, Repoman-2.3.12
Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org>

 dev-perl/Test-Strict/Manifest                   |  1 +
 dev-perl/Test-Strict/Test-Strict-0.470.0.ebuild | 26 +++++++++++++++++++++++++
 dev-perl/Test-Strict/metadata.xml               |  8 ++++++++
 3 files changed, 35 insertions(+)

diff --git a/dev-perl/Test-Strict/Manifest b/dev-perl/Test-Strict/Manifest
new file mode 100644
index 00000000000..ea72ecb1585
--- /dev/null
+++ b/dev-perl/Test-Strict/Manifest
@@ -0,0 +1 @@
+DIST Test-Strict-0.47.tar.gz 20679 BLAKE2B e72eef42fdb7c0e354147c06f4e7c418d5c302d0bca662995042d7046fd9deae3ae6b12fa0f780aff8d6f0e5cab52db76184d99471d130ce18bfd6c00657dddb SHA512 56ffc488cb2502af228ad03f3da7bf11f04c0cacc7f1ea13b3aa8e0578f0df36a9be092f71db973748c8db15f45873a384f2e24844468b9a300d2386692c21b9

diff --git a/dev-perl/Test-Strict/Test-Strict-0.470.0.ebuild b/dev-perl/Test-Strict/Test-Strict-0.470.0.ebuild
new file mode 100644
index 00000000000..e4f6cbea1b4
--- /dev/null
+++ b/dev-perl/Test-Strict/Test-Strict-0.470.0.ebuild
@@ -0,0 +1,26 @@
+# Copyright 1999-2019 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=6
+
+DIST_AUTHOR=MANWAR
+DIST_VERSION=0.47
+inherit perl-module
+
+DESCRIPTION="Check syntax, presence of use strict; and test coverage"
+
+SLOT="0"
+KEYWORDS="~amd64"
+IUSE="test"
+
+RDEPEND="
+	virtual/perl-File-Spec
+	virtual/perl-File-Temp
+"
+DEPEND="${RDEPEND}
+	virtual/perl-ExtUtils-MakeMaker
+	test? (
+		dev-perl/IO-stringy
+		virtual/perl-Test-Simple
+	)
+"

diff --git a/dev-perl/Test-Strict/metadata.xml b/dev-perl/Test-Strict/metadata.xml
new file mode 100644
index 00000000000..2b9a936fc0a
--- /dev/null
+++ b/dev-perl/Test-Strict/metadata.xml
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+  <maintainer type="project">
+    <email>perl@gentoo.org</email>
+    <name>Gentoo Perl Project</name>
+  </maintainer>
+</pkgmetadata>


             reply	other threads:[~2019-04-03 15:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-03 15:46 Andreas K. Hüttel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-29  0:58 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Test-Strict/ Andreas K. Hüttel
2021-12-10 17:21 Andreas K. Hüttel
2024-10-11  3:39 Sam James

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=1554306346.bddf0df8a80ed05e196546daafc13b9848069cc9.dilfridge@gentoo \
    --to=dilfridge@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