Commit graph

13 commits

Author SHA1 Message Date
wiz
86a78fce2e Bump PKGREVISION for perl-5.24. 2016-06-08 19:22:13 +00:00
wen
dc58b6b239 Update to 0.018
Upstream changes:
0.018     2015-12-11 11:55:44-05:00 America/New_York

  - Generated from ETHER/YAML-Tiny-1.69.tar.gz

  - See https://metacpan.org/changes/release/ETHER/YAML-Tiny-1.69 for details

0.017     2015-08-04 06:02:12-04:00 America/New_York (TRIAL RELEASE)

  - Generated from ETHER/YAML-Tiny-1.69.tar.gz
2016-01-08 14:42:53 +00:00
agc
d9e4cfe05d 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.
2015-11-03 03:27:11 +00:00
wiz
0982effce2 Recursive PKGREVISION bump for all packages mentioning 'perl',
having a PKGNAME of p5-*, or depending such a package,
for perl-5.22.0.
2015-06-12 10:48:20 +00:00
mef
d8bd3039e5 Update 0.014 to 0.016
---------------------
0.016     2015-05-19 05:34:02-04:00 America/New_York
  - Generated from ETHER/YAML-Tiny-1.67.tar.gz

0.015     2015-05-11 22:01:58-04:00 America/New_York (TRIAL RELEASE)
  - Generated from ETHER/YAML-Tiny-1.67.tar.gz
2015-05-22 23:38:45 +00:00
mef
948d6a814c Update 0.012 to 0.014
---------------------
0.014     2015-03-16 19:22:12-04:00 America/New_York
  - Generated from ETHER/YAML-Tiny-1.66.tar.gz

0.013     2015-03-16 11:32:04-04:00 America/New_York
  - Generated from ETHER/YAML-Tiny-1.65.tar.gz
2015-04-09 00:44:34 +00:00
wiz
7eeb51b534 Bump for perl-5.20.0.
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.
2014-05-29 23:35:13 +00:00
hiramatsu
3474d04df9 Update devel/p5-CPAN-Meta-YAML to 0.012.
Changes from previous:
----------------------
0.012     2014-02-24 13:07:18-05:00 America/New_York

  - Generated from ETHER/YAML-Tiny-1.61.tar.gz

0.011     2014-02-13 20:30:30-05:00 America/New_York

  - Generated from ETHER/YAML-Tiny-1.60.tar.gz

0.010     2013-09-23 13:11:20 America/New_York

  - Generated from ETHER/YAML-Tiny-1.55.tar.gz

  - Fix broken test when copying from YAML-Tiny

  - updated Makefile.PL logic to support PERL_NO_HIGHLANDER

0.009     2013-09-23 10:16:19 America/New_York

  - Generated from ETHER/YAML-Tiny-1.55.tar.gz

  - Makefile.PL will use UNINST=1 on old perls that might have
    an old version incorrectly installed into the core library path
2014-04-07 04:51:23 +00:00
wiz
d2ca14a3f1 Bump all packages for perl-5.18, that
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.
2013-05-31 12:39:57 +00:00
asau
e1ab7079b6 Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days. 2012-10-31 11:16:30 +00:00
wiz
8b5d49eb78 Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.

I hope that's all of them.
2012-10-03 21:53:53 +00:00
sno
556152efeb Updating package for Perl5 module CPAN::Meta::YAML from CPAN in
devel/p5-CPAN-Meta-YAML from 0.007 to 0.008.

Upstream changes:
0.008     2012-03-14 17:13:24 EST5EDT
  - Generated from ADAMK/YAML-Tiny-1.51.tar.gz
  - Updated from YAML-Tiny to fix compatibility with older Scalar::Utils
2012-03-22 13:40:07 +00:00
sno
7166495b14 Importing package for CPAN module CPAN::Meta::YAML version 0.007 into
devel/p5-CPAN-Meta-YAML as dependency of scheduled update of package
for CPAN module CPAN::Meta in devel/p5-CPAN-Meta.

This module implements a subset of the YAML specification for use in
reading and writing CPAN metadata files like META.yml and MYMETA.yml.
It should not be used for any other general YAML parsing or generation
task.

NOTE: META.yml (and MYMETA.yml) files should be UTF-8 encoded. Users
are responsible for proper encoding and decoding. In particular, the
read and write methods do not support UTF-8 and should not be used.
2012-02-20 13:16:18 +00:00