Commit graph

5 commits

Author SHA1 Message Date
seb
e8328761a2 Use buildlink2. Use perl5/module.mk. 2002-10-27 20:48:55 +00:00
jlam
cc4128d97e Buildlinkify, in the sense that only the perl headers are found in
${PREFIX} -- everything else is pickup up from ${BUILDLINK_DIR}.
2001-11-26 06:49:36 +00:00
zuntum
431e7a7dda Move pkg/ files into package's toplevel directory 2001-11-01 02:15:23 +00:00
veego
63ad910dee 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 15:20:01 +00:00
jlam
42500b7205 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 02:12:59 +00:00