Age | Commit message (Collapse) | Author | Files | Lines |
|
pkgsrc changes:
- Adding license (perl5 license)
Upstream changes:
1.04 Sun 12 Jul 2009
- Upgrading to Module::Install::DSL 0.91
- Sometimes there is no Config_heavy.pl
- Updating dependencies to rid myself of memory leaks
|
|
- Updating package for p5 module prefork to 1.03
Upstream changes:
1.03 Mon 21 Apr 2008
- Upgrading to Module::Install 0.83
- Preload all of Config.pm
|
|
to trigger/signal a rebuild for the transition 5.8.8 -> 5.10.0.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=...").
|
|
|
|
1.02 Fri 23 Nov 2007
- Upgrading to Module::Install 0.68
|
|
can handle packages having no PLIST files.
|
|
Patch provided by Martin Wilke via PR 34366.
NOTE: No need to depend on p5-ExtUtils-AutoInstall>=0.59 now, so remove it.
Changes:
1.01 Tue 25 Jul 2006
- Imported from CVS to svn repository
|
|
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
|
|
1.00 Thu Sep 8 2005
- Has proven itself stable, promoting to 1.00
- Various small POD clean ups
- Adding default notifier to auto-compile the CGI functions
- Rebuilding with a newer (better) Module::Install
|
|
of Perl files to deal with the perl-5.8.7 update that moved all
pkgsrc-installed Perl files into the "vendor" directories.
|
|
These paths are now relative to PERL5_PACKLIST_DIR, which currently
defaults to ${PERL5_SITEARCH}. There is no change to the binary
packages.
|
|
|
|
The prefork pragma is intended to allow module writers to optimise
module loading for both scenarios with as little additional code
as possible.
The prefork.pm is intended to serve as a central and optional
marshalling point for state detection (are we running in procedural
or pre-forking mode) and to act as a relatively light-weight module
loader.
|