kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/www/p5-Apache-SSI/Makefile

20 lines
549 B
Makefile
Raw Normal View History

Use buildlink2. Use perl5/module.mk.
2002-10-27 21:48:55 +01:00
# $NetBSD: Makefile,v 1.4 2002/10/27 20:49:01 seb Exp $
p5-Apache-SSI - implements Server Side Includes in Perl Apache::SSI implements the functionality of mod_include for handling server-parsed html documents. It runs under Apache's mod_perl. In my mind, there are two main reasons you might want to use this module: you can sub-class it to implement your own custom SSI directives, and/or you can parse the output of other mod_perl handlers, or send the SSI output through another handler (use Apache::Filter to do this).
2001-10-01 04:12:59 +02:00
DISTNAME= Apache-SSI-2.16
PKGNAME= p5-${DISTNAME}
SVR4 packages have a limit of 9 chars for a package name. The automatic truncation in gensolpkg doesn't work for packages which have the same package name for the first 5-6 chars. e.g. amanda-server and amanda-client would be named amanda and amanda. Now, we add a SVR4_PKGNAME and use amacl for amanda-client and amase for amanda-server. All svr4 packages also have a vendor tag, so we have to reserve some chars for this tag, which is normaly 3 or 4 chars. Thats why we can only use 6 or 5 chars for SVR4_PKGNAME. I used 5 for all the packages, to give the vendor tag enough room. All p5-* packages and a few other packages have now a SVR4_PKGNAME.
2001-10-18 17:20:01 +02:00
SVR4_PKGNAME= p5ass
p5-Apache-SSI - implements Server Side Includes in Perl Apache::SSI implements the functionality of mod_include for handling server-parsed html documents. It runs under Apache's mod_perl. In my mind, there are two main reasons you might want to use this module: you can sub-class it to implement your own custom SSI directives, and/or you can parse the output of other mod_perl handlers, or send the SSI output through another handler (use Apache::Filter to do this).
2001-10-01 04:12:59 +02:00
CATEGORIES= www perl5
MASTER_SITES= ${MASTER_SITE_PERL_CPAN:=Apache/}
MAINTAINER= packages@netbsd.org
COMMENT= perl5 module to implement Server Side Includes
DEPENDS+= p5-HTML-SimpleParse>=0.06:../../www/p5-HTML-SimpleParse
Use buildlink2. Use perl5/module.mk.
2002-10-27 21:48:55 +01:00
USE_BUILDLINK2= YES
Buildlinkify, in the sense that only the perl headers are found in ${PREFIX} -- everything else is pickup up from ${BUILDLINK_DIR}.
2001-11-26 07:49:36 +01:00
PERL5_PACKLIST= ${PERL5_SITEARCH}/auto/Apache/SSI/.packlist
p5-Apache-SSI - implements Server Side Includes in Perl Apache::SSI implements the functionality of mod_include for handling server-parsed html documents. It runs under Apache's mod_perl. In my mind, there are two main reasons you might want to use this module: you can sub-class it to implement your own custom SSI directives, and/or you can parse the output of other mod_perl handlers, or send the SSI output through another handler (use Apache::Filter to do this).
2001-10-01 04:12:59 +02:00
Use buildlink2. Use perl5/module.mk.
2002-10-27 21:48:55 +01:00
.include "../../www/ap-perl/buildlink2.mk"
.include "../../lang/perl5/module.mk"
p5-Apache-SSI - implements Server Side Includes in Perl Apache::SSI implements the functionality of mod_include for handling server-parsed html documents. It runs under Apache's mod_perl. In my mind, there are two main reasons you might want to use this module: you can sub-class it to implement your own custom SSI directives, and/or you can parse the output of other mod_perl handlers, or send the SSI output through another handler (use Apache::Filter to do this).
2001-10-01 04:12:59 +02:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink