svn commit: r466651 - in head/devel: . p5-Test-Log-Log4perl

[Sunpoet Po-Chuan Hsieh]

Author: sunpoet
Date: Fri Apr  6 16:26:09 2018
New Revision: 466651
URL: https://svnweb.freebsd.org/changeset/ports/466651

Log:
  Add p5-Test-Log-Log4perl 0.32
  
  Test::Log::Log4perl can be used to test that you're logging the right thing with
  Log::Log4perl. It checks that we get what, and only what, we expect logged by
  your code.
  
  The basic process is very simple. Within your test script you get one or more
  loggers from Test::Log::Log4perl with the get_logger method just like you would
  with Log::Log4perl. You're going to use these loggers to declare what you think
  the code you're going to test should be logging.
  
  WWW: http://search.cpan.org/dist/Test-Log-Log4perl/

Added:
  head/devel/p5-Test-Log-Log4perl/
  head/devel/p5-Test-Log-Log4perl/Makefile   (contents, props changed)
  head/devel/p5-Test-Log-Log4perl/distinfo   (contents, props changed)
  head/devel/p5-Test-Log-Log4perl/pkg-descr   (contents, props changed)
  head/devel/p5-Test-Log-Log4perl/pkg-plist   (contents, props changed)
Modified:
  head/devel/Makefile

Modified: head/devel/Makefile
==============================================================================
--- head/devel/Makefile	Fri Apr  6 16:08:02 2018	(r466650)
+++ head/devel/Makefile	Fri Apr  6 16:26:09 2018	(r466651)
@@ -3491,6 +3491,7 @@
     SUBDIR += p5-Test-LeakTrace
     SUBDIR += p5-Test-LectroTest
     SUBDIR += p5-Test-LoadAllModules
+    SUBDIR += p5-Test-Log-Log4perl
     SUBDIR += p5-Test-Log4perl
     SUBDIR += p5-Test-LongString
     SUBDIR += p5-Test-Manifest

Added: head/devel/p5-Test-Log-Log4perl/Makefile
==============================================================================
--- /dev/null	00:00:00 1970	(empty, because file is newly added)
+++ head/devel/p5-Test-Log-Log4perl/Makefile	Fri Apr  6 16:26:09 2018	(r466651)
@@ -0,0 +1,23 @@
+# Created by: Po-Chuan Hsieh <sunpoet at FreeBSD.org>
+# $FreeBSD$
+
+PORTNAME=	Test-Log-Log4perl
+PORTVERSION=	0.32
+CATEGORIES=	devel perl5
+MASTER_SITES=	CPAN
+PKGNAMEPREFIX=	p5-
+
+MAINTAINER=	sunpoet at FreeBSD.org
+COMMENT=	Test log4perl
+
+LICENSE=	ART10 GPLv1+
+LICENSE_COMB=	dual
+
+BUILD_DEPENDS=	p5-Log-Log4perl>=0:devel/p5-Log-Log4perl
+RUN_DEPENDS:=	${BUILD_DEPENDS}
+TEST_DEPENDS=	p5-Test-Exception>=0:devel/p5-Test-Exception
+
+USE_PERL5=	configure
+USES=		perl5
+
+.include <bsd.port.mk>

Added: head/devel/p5-Test-Log-Log4perl/distinfo
==============================================================================
--- /dev/null	00:00:00 1970	(empty, because file is newly added)
+++ head/devel/p5-Test-Log-Log4perl/distinfo	Fri Apr  6 16:26:09 2018	(r466651)
@@ -0,0 +1,3 @@
+TIMESTAMP = 1523025949
+SHA256 (Test-Log-Log4perl-0.32.tar.gz) = 23ebbb05893a05ebfe397fbce55152df8f9d6500125a8042f1aa6cfa93fc23c4
+SIZE (Test-Log-Log4perl-0.32.tar.gz) = 28530

Added: head/devel/p5-Test-Log-Log4perl/pkg-descr
==============================================================================
--- /dev/null	00:00:00 1970	(empty, because file is newly added)
+++ head/devel/p5-Test-Log-Log4perl/pkg-descr	Fri Apr  6 16:26:09 2018	(r466651)
@@ -0,0 +1,10 @@
+Test::Log::Log4perl can be used to test that you're logging the right thing with
+Log::Log4perl. It checks that we get what, and only what, we expect logged by
+your code.
+
+The basic process is very simple. Within your test script you get one or more
+loggers from Test::Log::Log4perl with the get_logger method just like you would
+with Log::Log4perl. You're going to use these loggers to declare what you think
+the code you're going to test should be logging.
+
+WWW: http://search.cpan.org/dist/Test-Log-Log4perl/

Added: head/devel/p5-Test-Log-Log4perl/pkg-plist
==============================================================================
--- /dev/null	00:00:00 1970	(empty, because file is newly added)
+++ head/devel/p5-Test-Log-Log4perl/pkg-plist	Fri Apr  6 16:26:09 2018	(r466651)
@@ -0,0 +1,2 @@
+%%SITE_PERL%%/Test/Log/Log4perl.pm
+%%PERL5_MAN3%%/Test::Log::Log4perl.3.gz