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.
---------------------
1.009 2014-07-03 13:17:48-04:00 America/New_York
[FIXED]
- s/0.95/0.96/ in t/File_pushd.t
1.008 2014-07-03 13:03:30-04:00 America/New_York
[FIXED]
- Require a newer version of Test::More
1.007 2014-05-30 23:59:02-04:00 America/New_York
[FIXED]
- Fixed a testing edge case on Windows
1.006 2014-03-27 15:29:36-04:00 America/New_York
[DOCUMENTED]
- Noted that multiple pushd objects in a lexical scope are not
destroyed in a predictable order
[CHANGED]
- Modernized Dist::Zilla configuration and repo support files
1.001.
Upstream changes:
1.001 2011-09-14 22:49:56 America/New_York
- updated docs to clarify that pushd() and tempd() croak on errors
- if tempd() croaks, error appears at tempd()'s caller, not from within
tempd() itself
- warnings enabled if perl version >= 5.006
- adds 'untaint_pattern' option with a passable default
File::pushd does a temporary chdir that is easily and automatically reverted,
similar to pushd in some Unix command shells. It works by creating an object
that caches the original working directory. When the object is destroyed, the
destructor calls chdir to revert to the original working directory. By storing
the object in a lexical variable with a limited scope, this happens
automatically at the end of the scope.
