-------------------
0.42 2015-02-14
- improve deprecation docs
0.41 2015-02-14
[DEPRECATIONS]
- revert the decision to not deprecate UMASK=0, re-deprecating GH #5
0.40 2013-11-15
- fix prototype mismatch with chmod() when autodie is used. GH #3 (arrestee)
[DEPRECATIONS]
- undeprecating the default of $UMASK is true
tested against my local chmod and it does obey umask. This will no
longer be removed.
0.39 2013-09-14
- fix tests failing to run as user with override privileges
RT #88543 ( zefram )
- add more tests
0.38 2013-09-09
- fix sticky bit tests for BSD ( Slaven ReziÄ<87> )
- disable windows tests
0.37 2013-09-08
- verify and fix RT #78107 chmod('o+t') should set sticky-bit like unix
chmod o+t
0.36 2013-09-08
- improve Pod using Pod::Weaver, this will allow better linking on web
interfaces
0.35 2013-09-08
- add read/write tests
- remove REVISIONS from pod
- add Test::PodSpelling, and fix spelling errors
0.34 2013-09-08
- fix basic.t to not fail on windows
0.33 2013-09-07
[DEPRECATIONS]
- $UMASK is true, this behavior is surprising if you're used to UNIX chmod
[NEWS]
- new maintainer Caleb Cushing
- migrate to Dist::Zilla
- add tests (note test failures are likely to be a result of new tests,
the code hasn't really changed)
Problems found with existing digests:
Package memconf distfile memconf-2.16/memconf.gz
b6f4b736cac388dddc5070670351cf7262aba048 [recorded]
95748686a5ad8144232f4d4abc9bf052721a196f [calculated]
Problems found locating distfiles:
Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9
Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz
Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz
Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz
Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz
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.
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!
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=...").
