Navigation:
Browse pkgsrc
(this page)| 2006-10-05 00:04:11 by Thomas Klausner | Files touched by this commit (30) |
Log message: Update MASTER_SITES and/or HOMEPAGE, from Sergey Svishchev. |
2005-08-06 08:19:41 by Johnny C. Lam | Files touched by this commit (634) |  |
Log message: Bump the PKGREVISIONs of all (638) packages that hardcode the locations of Perl files to deal with the perl-5.8.7 update that moved all pkgsrc-installed Perl files into the "vendor" directories. |
| 2005-07-16 03:19:27 by Johnny C. Lam | Files touched by this commit (273) |
Log message: Get rid of USE_PERL5. The new way to express needing the Perl executable around at either build-time or at run-time is: USE_TOOLS+= perl # build-time USE_TOOLS+= perl:run # run-time Also remove some places where perl5/buildlink3.mk was being included by a package Makefile, but all that the package wanted was the Perl executable. |
| 2005-07-13 20:01:49 by Johnny C. Lam | Files touched by this commit (578) |
Log message:
Turn PERL5_PACKLIST into a relative path instead of an absolute path.
These paths are now relative to PERL5_PACKLIST_DIR, which currently
defaults to ${PERL5_SITEARCH}. There is no change to the binary
packages.
|
| 2005-05-23 10:26:17 by Roland Illig | Files touched by this commit (270) |
Log message: Removed trailing white-space. |
| 2005-04-11 23:48:17 by Todd Vierling | Files touched by this commit (3539) |
Log message: Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used. |
| 2005-02-24 15:08:42 by Thomas Klausner | Files touched by this commit (277) |
Log message: Add RMD160 checksums. |
2004-06-22 23:34:51 by Adrian Portelli | Files touched by this commit (5) |  |
Log message:
Import SpeedyCGI v2.22 from pkgsrc-wip
Ok'ed wiz@/snj@
SpeedyCGI is a way to run perl scripts persistently, which can make them run
much more quickly. A script can be made to to run persistently by changing
the interpreter line at the top of the script from:
#!${LOCALBASE}/bin/perl
to
#!${LOCALBASE}/bin/speedy
After the script is initially run, instead of exiting, the perl interpreter
is kept running. During subsequent runs, this interpreter is used to handle
new executions instead of starting a new perl interpreter each time. A very
fast frontend program, written in C, is executed for each request. This fast
frontend then contacts the persistent Perl process, which is usually already
running, to do the work and return the results.
|
New packages: