openbsd-ports/devel/p5-Log-Agent/Makefile

# $OpenBSD: Makefile,v 1.15 2016/03/20 19:56:27 naddy Exp $

COMMENT=	abstraction layer for logging and tracing

MODULES=	cpan
PKG_ARCH=	*
DISTNAME =	Log-Agent-1.001
CATEGORIES=	devel

# Artistic License
PERMIT_PACKAGE_CDROM=	Yes

.include <bsd.port.mk>
Remove SHARED_ONLY from all CPAN Perl ports and the cpan and perl MODULES. Add WANTLIB+=perl and PKG_ARCH=* as appropriate. 2016-03-20 19:56:05 +00:00			`# $OpenBSD: Makefile,v 1.15 2016/03/20 19:56:27 naddy Exp $`
Initial import of Log-Agent 0.304 Log::Agent is a general logging framework aimed at reusable modules. Instead of having modules insist on using their own logging reporting (by hardwiring calls to warn() or syslog()) which can conflict with the final application's choice, one may use logwarn() for instance to emit a warning. From Andrew Dalgleish <openbsd@andrewdalgleish.dyndns.org> 2003-04-13 16:20:20 +00:00
Remove quotes surrounding COMMENT/PERMIT_/BROKEN 2007-09-16 02:52:56 +00:00			`COMMENT= abstraction layer for logging and tracing`
Initial import of Log-Agent 0.304 Log::Agent is a general logging framework aimed at reusable modules. Instead of having modules insist on using their own logging reporting (by hardwiring calls to warn() or syslog()) which can conflict with the final application's choice, one may use logwarn() for instance to emit a warning. From Andrew Dalgleish <openbsd@andrewdalgleish.dyndns.org> 2003-04-13 16:20:20 +00:00
switch about half of devel/p5-* to newest cpan practices 2006-11-25 16:32:33 +00:00			`MODULES= cpan`
Remove SHARED_ONLY from all CPAN Perl ports and the cpan and perl MODULES. Add WANTLIB+=perl and PKG_ARCH=* as appropriate. 2016-03-20 19:56:05 +00:00			`PKG_ARCH= *`
Update to p5-Log-Agent-1.001. 2015-12-03 14:55:41 +00:00			`DISTNAME = Log-Agent-1.001`
switch about half of devel/p5-* to newest cpan practices 2006-11-25 16:32:33 +00:00			`CATEGORIES= devel`
Initial import of Log-Agent 0.304 Log::Agent is a general logging framework aimed at reusable modules. Instead of having modules insist on using their own logging reporting (by hardwiring calls to warn() or syslog()) which can conflict with the final application's choice, one may use logwarn() for instance to emit a warning. From Andrew Dalgleish <openbsd@andrewdalgleish.dyndns.org> 2003-04-13 16:20:20 +00:00
			`# Artistic License`
			`PERMIT_PACKAGE_CDROM= Yes`

			`.include <bsd.port.mk>`