kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/devel/p5-File-Policy/Makefile

29 lines
669 B
Makefile
Raw Normal View History

This defines the policy for file I/O with modules such as File::Slurp::WithinPolicy. The purpose is to allow systems administrators to define locations and restrictions for applications' file I/O and give app developers a policy to follow. Note that the module doesn't ENFORCE the policy - application developers can choose to ignore it (and systems administrators can choose not to install their applications if they do!). You may control which policy gets applied by creating a File::Policy::Config module with an IMPLEMENTATION constant. You may write your own policy as a module within the File::Policy:: namespace. By default (if no File::Policy::Config is present), the File::Policy::Default policy gets applied which doesn't impose any restrictions and provides reasonable default locations for temporary and log files. WWW: http://search.cpan.org/dist/File-Policy/
2007-08-27 04:24:42 +02:00
# New ports collection makefile for: p5-File-Policy
# Date created: August 27, 2007
# Whom: Cheng-Lung Sung <clsung@FreeBSD.org>
#
# $FreeBSD$
#
PORTNAME= File-Policy
PORTVERSION= 1.005
CATEGORIES= devel perl5
MASTER_SITES= CPAN
PKGNAMEPREFIX= p5-
MAINTAINER= clsung@FreeBSD.org
COMMENT= Simple policy for file I/O functions
BUILD_DEPENDS= p5-Log-Trace>0:${PORTSDIR}/devel/p5-Log-Trace \
p5-File-Slurp>0:${PORTSDIR}/devel/p5-File-Slurp \
p5-Test-Assertions>0:${PORTSDIR}/devel/p5-Test-Assertions
At the moment 1385 ports use BUILD_DEPENDS= ${RUN_DEPENDS} and 450 ports use BUILD_DEPENDS:= ${RUN_DEPENDS}. This patch fixes ports that are currently broken. This is a temporary measure until we organically stop using := or someone(s) spend a lot of time changing all the ports over. Explicit duplication > := > = and this just moves ports one step to the left Approved by: portmgr
2012-01-21 18:40:15 +01:00
RUN_DEPENDS:= ${BUILD_DEPENDS}
This defines the policy for file I/O with modules such as File::Slurp::WithinPolicy. The purpose is to allow systems administrators to define locations and restrictions for applications' file I/O and give app developers a policy to follow. Note that the module doesn't ENFORCE the policy - application developers can choose to ignore it (and systems administrators can choose not to install their applications if they do!). You may control which policy gets applied by creating a File::Policy::Config module with an IMPLEMENTATION constant. You may write your own policy as a module within the File::Policy:: namespace. By default (if no File::Policy::Config is present), the File::Policy::Default policy gets applied which doesn't impose any restrictions and provides reasonable default locations for temporary and log files. WWW: http://search.cpan.org/dist/File-Policy/
2007-08-27 04:24:42 +02:00
PERL_CONFIGURE= yes
MAN3= File::Policy.3 \
File::Policy::Default.3 \
File::Slurp::WithinPolicy.3
.include <bsd.port.mk>
Reference in a new issue Copy permalink