Log message:
Update to 2.000005

Upstream changes:
2.000005 - 2018-04-20
  - update internal list of warnings for categories added in 5.28.0 (no
    behaviour change)

2.000004 - 2018-04-19
  - update bundled ExtUtils::HasCompiler to 0.021
  - update internal list of warnings for categories added in 5.26.0 (no
    behavior change)

Log message:
Recursive revbump from lang/perl5 5.26.0

Log message:
Bump PKGREVISION for perl-5.24.

Log message:
Updated p5-strictures to 2.000003.

2.000003 - 2016-04-19
  - update bundled ExtUtils::HasCompiler to 0.013 to fix potential false
    negative (RT#113637)
  - list optional XS dependencies as suggests rather than recommends (RT#107393)

Log message:
Update p5-strictures to 2.000002:

2.000002 - 2015-11-04
  - use ExtUtils::HasCompiler to detect compiler rather than ExtUtils::CBuilder
  - more comprehensive testing

Log message:
Add SHA512 digests for distfiles for devel category

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.

Log message:
Update to 2.000001

Upstream changes:
2.000001 - 2015-06-28
  - update for perl 5.22 warning categories
  - avoid using goto &UNIVERSAL::VERSION on perl 5.8, since it segfaults some
    builds
  - also detect development directories based on .bzr directory
  - various test cleanups

Log message:
Recursive PKGREVISION bump for all packages mentioning 'perl',
having a PKGNAME of p5-*, or depending such a package,
for perl-5.22.0.

Log message:
Update to 2.0:

2.000000 - 2015-02-26
  * Incompatible Changes
    - strictures 2 fatalizes only a subset of warnings.  Some warning
      categories are not safe to catch, or just inappropriate to have fatal.
      Existing code looking like 'use strictures 1;' will continue to get the
      old behavior of fatalizing all errors.  The new behavior will take effect
      when no version or version 2 is specified.

Log message:
Update to 1.005006:

1.005006 - 2015-01-30
  - fix extra checks triggering on paths starting with t, xt, lib, or blib,
    rather than only triggering on those directories.
  - avoid stat checks for VCS directories until we are in an appropriately
    named file
  - various cleanups in test files