Date: Fri, 11 May 2018 10:22:26 +0000 (UTC) From: Kurt Jaeger <pi@FreeBSD.org> To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r469622 - in head/devel: . p5-Call-Context Message-ID: <201805111022.w4BAMQpI038132@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: pi Date: Fri May 11 10:22:25 2018 New Revision: 469622 URL: https://svnweb.freebsd.org/changeset/ports/469622 Log: New port: devel/p5-Call-Context Sanity-check calling context If your function only expects to return a list, then a call in some other context is, by definition, an error. The problem is that, depending on how the function is written, it may actually do something expected in testing, but then in production act differently. WWW: http://search.cpan.org/dist/Call-Context/ Added: head/devel/p5-Call-Context/ head/devel/p5-Call-Context/Makefile (contents, props changed) head/devel/p5-Call-Context/distinfo (contents, props changed) head/devel/p5-Call-Context/pkg-descr (contents, props changed) Modified: head/devel/Makefile Modified: head/devel/Makefile ============================================================================== --- head/devel/Makefile Fri May 11 09:46:40 2018 (r469621) +++ head/devel/Makefile Fri May 11 10:22:25 2018 (r469622) @@ -2044,6 +2044,7 @@ SUBDIR += p5-Cache-Simple-TimedExpiry SUBDIR += p5-Cairo-GObject SUBDIR += p5-Calendar-Simple + SUBDIR += p5-Call-Context SUBDIR += p5-Callback-Frame SUBDIR += p5-Canary-Stability SUBDIR += p5-Capture-Tiny Added: head/devel/p5-Call-Context/Makefile ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/devel/p5-Call-Context/Makefile Fri May 11 10:22:25 2018 (r469622) @@ -0,0 +1,26 @@ +# $FreeBSD$ + +PORTNAME= Call-Context +PORTVERSION= 0.02 +CATEGORIES= devel perl5 +MASTER_SITES= CPAN +MASTER_SITE_SUBDIR= CPAN:FELIPE +PKGNAMEPREFIX= p5- + +MAINTAINER= pi@FreeBSD.org +COMMENT= Sanity-check calling context + +LICENSE= ART10 GPLv1+ +LICENSE_COMB= dual + +NO_ARCH= yes + +USES= perl5 +USE_PERL5= configure +PLIST_FILES= ${SITE_PERL_REL}/Call/Context.pm \ + ${SITE_MAN3_REL}/Call::Context.3.gz + +pre-install: + ${RM} ${WRKSRC}/blib/lib/Call/README.pod + +.include <bsd.port.mk> Added: head/devel/p5-Call-Context/distinfo ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/devel/p5-Call-Context/distinfo Fri May 11 10:22:25 2018 (r469622) @@ -0,0 +1,3 @@ +TIMESTAMP = 1526032556 +SHA256 (Call-Context-0.02.tar.gz) = b80d977f1df0e08bda2808124cd7218ad83f802e1a54aa258e17748ff5c02a0a +SIZE (Call-Context-0.02.tar.gz) = 10046 Added: head/devel/p5-Call-Context/pkg-descr ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/devel/p5-Call-Context/pkg-descr Fri May 11 10:22:25 2018 (r469622) @@ -0,0 +1,8 @@ +Sanity-check calling context + +If your function only expects to return a list, then a call in some +other context is, by definition, an error. The problem is that, +depending on how the function is written, it may actually do something +expected in testing, but then in production act differently. + +WWW: http://search.cpan.org/dist/Call-Context/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201805111022.w4BAMQpI038132>