pkgsrc changes:
- add license
- tidy
Upstream changes:
Release 0.69 - 28th August 2010
- Correctly report on C<my $x = $y || return> and other shortcuts.
- Put end to end tests in t/e2e.
- Add test for regexp eval fail (Florian Ragwitz).
- Fix some warnings from strict compilers (Florian Ragwitz).
- Allow tests to run in parallel (Florian Ragwitz).
- Test against 5.13.* development releases.
- We now require Test::More to run the tests.
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:
Release 0.68 - 5th August 2010
- Fix gcov2perl to work with large numbers (Thomas Dorner) (rt 45028).
- Fix "gcov -l" include files (Thomas Dorner) (rt 44864).
- Test against 5.12.1.
- Gross workaround for for regexp evals (Florian Ragwitz).
Upstream changes:
Release 0.66 - 12th April 2010
- Move to faster method of collecting data. Could be up to twice as fast now.
- Add -replace_ops options to be able to revert to previous collection method.
- Test against 5.12.0 and update tests as necessry.
- Work better with non-existent databases.
- XS fixes related to overriding ops rather than replacing runops
(Florian Ragwitz).
- Don't chmod created directories (mkdir should suffice).
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=...").
Collection.
The Perl 5 module Devel::Cover provides code coverage metrics for
Perl. Code coverage metrics describe how thoroughly tests exercise
code. By using Devel::Cover you can discover areas of code not
exercised by your tests and determine which tests to create to
increase coverage. Code coverage can be considered as an indirect
measure of quality.
