Issues found with existing distfiles:
distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip
distfiles/fortran-utils-1.1.tar.gz
distfiles/ivykis-0.39.tar.gz
distfiles/enum-1.11.tar.gz
distfiles/pvs-3.2-libraries.tgz
distfiles/pvs-3.2-linux.tgz
distfiles/pvs-3.2-solaris.tgz
distfiles/pvs-3.2-system.tgz
No changes made to these distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
* Remove CImpl and simplify structure into just Cache::FastMmap module making
all XS calls just function calls in Cache::FastMmap namespace
Changes 1.38:
* Fix build process that was completely broken after moving files around into
different directories
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.
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=..."), minus the packages updated after
the perl package update.
sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
Upstream changes:
1.35 Fri Feb 19 12:45 2010
- Fix for returning potential bug that returns old stored data. Could
occur if you mix deletes (thanks Darrell Bishop)
- Updating package for p5 module Cache::FastMmap from 1.30 to 1.34
- Adjusting LICENSE
Upstream changes:
1.34 Fri Jun 19 12:00 2009
- perldoc fix (thanks Jonathan Yu)
1.33 Thu Jun 18 12:00 2009
- Update version in META.yml
1.32 Thu Jun 18 11:55 2009
- Better LiveCaches tracking via DESTROY
1.31 Thu Jun 18 11:40 2009
- when in raw_values => 0 mode, the write_cb is now
correctly called with thawed data, rather than the
raw frozen data
- empty_on_exit correctly called even when a global
cache is left at interpreter exit time (required
Scalar::Util qw(weaken) for object tracking)
- Updating package for p5 module of Cache::FastMmap from 1.28 to 1.29
- Setting license to gnu-gpl-v2
Upstream changes:
- get_and_set() returns new value + didstore boolean
if called in list context
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=...").
ChangeLog:
1.28 Fri Jun 27 11:05 2008
- get_and_set() returns new value + didstore boolean
if called in list context
1.27 Wed Jun 18 17:15 2008
- Fix non-ansi C code
- Remove debug flags
A shared memory cache through an mmap'ed file. Its core is written
in C for performance. It uses fcntl locking to ensure multiple
processes can safely access the cache at the same time. It uses
a basic LRU algorithm to keep the most used entries in the cache.
