Next | Query returned 36 messages, browsing 31 to 40 | previous

History of commit frequency

CVS Commit History:


   2006-03-04 22:31:14 by Johnny C. Lam | Files touched by this commit (2257)
Log message:
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
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.
   2005-11-23 00:14:52 by Thomas Klausner | Files touched by this commit (2)
Log message:
Update to 1.00:

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
   2005-08-06 08:19:41 by Johnny C. Lam | Files touched by this commit (634) | Package updated
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-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-06-26 17:27:19 by Stoned Elipot | Files touched by this commit (1)
Log message:
Fix build: this needs p5-ExtUtils-AutoInstall to build.
   2005-06-24 21:58:09 by Thomas Klausner | Files touched by this commit (4) | Imported package
Log message:
Initial import of p5-prefork-0.04:

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.


Next | Query returned 36 messages, browsing 31 to 40 | previous