---------------------------
2.150005 2015-06-09 19:08:44-06:00 America/Denver
[TESTING]
- Changed some test data from UTF-8 to ASCII
2.150004 2015-05-19 11:25:53-04:00 America/New_York (TRIAL RELEASE)
[DOCUMENTED]
- Noted explicitly that historical META spec files are licensed under
the same terms as Perl
[TESTING]
- Added test for 'x_deprecated' field in "provides"
[META]
- declared extra developer prereq
2.150003 2015-04-21 19:41:15-04:00 America/New_York (TRIAL RELEASE)
[CHANGED]
- Serialized CPAN::Meta objects now include a x_serialization_backend
entry
2.150002 2015-04-19 01:00:10+02:00 Europe/Berlin (TRIAL RELEASE)
[CHANGED]
- Metadata merging now does deep hash merging as long as keys
don't conflict
{perl>=5.16.6,p5-ExtUtils-ParseXS>=3.15}:../../devel/p5-ExtUtils-ParseXS
since pkgsrc enforces the newest perl version anyway, so they
should always pick perl, but sometimes (pkg_add) don't due to the
design of the {,} syntax.
No effective change for the above reason.
Ok joerg
[DOCUMENTED]
- Include allowed values for license field in 1.x historic licenses rather
than linking to Module::Build
- Documented when fragment merging became available
-------------------
2.143240 2014-11-20 10:26:30-05:00 America/New_York
[FIXED]
- Give correct path in nested merges such as resources
- Removed strings test that should have been removed when
CPAN::Meta::Requirements was removed to a separate dist
Upstream changes:
2.142690 2014-09-26 11:06:34-04:00 America/New_York
[DOCUMENTED]
- Clarified that no_index is a list of exclusions, and that indexers
should generally exclude 'inc', 'xt' and 't' as well.
2.142060 2014-07-25 13:30:06-04:00 America/New_York
[ADDED]
- CPAN::Meta::Merge is a new class for merging two possibly overlapping
instances of metadata. It will accept both CPAN::Meta objects and
(possibly incomplete) hashrefs of metadata.
- Clarified use of 'file' for the 'provides' field in the Spec
- Added ability for CPAN::Meta::Converter to convert metadata fragments
(incomplete portions of a metadata structure)
- Optimized internal use of JSON for datastructure cloning
- Removed dependency on List::Util 1.33
- Clarified language around 'dynamic_config' in the Spec
- A change to the default meta-spec URL in 2.140630 from search.cpan.org
to metacpan.org broke Module::Build and ExtUtils::MakeMaker. This
reverts that change. Also added the missing change note to the prior
version.
- Default meta-spec URL points to metacpan.org instead of search.cpan.org
- Added a 'load_string' method that guesses whether the string
is YAML or JSON
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.
2.133380 2013-12-03 23:01:07 America/New_York
[FIXED]
- Improved bad version handling during META conversion
- When downgrading multiple licenses to version 1.x META formats, if all
the licenses are open source, the downgraded license will be
"open_source", not "unknown"
Upstream changes:
2.132140 2013-08-02 11:54:17 America/New_York
[DOCUMENTATION]
- Fixed some typos in CPAN::Meta::Spec
[OTHER]
- migrated repository to Perl-Toolchain-Gang organization on Github and
updated metadata accordingly
2.131560 2013-06-05 15:26:36 America/New_York
[DOCUMENTATION]
- Replaced CPAN::Meta SYNOPSIS with code that actually works
2.131490 2013-05-29 14:15:16 America/New_York
[BUGFIX]
- Downconversion of custom resources was not dropping the leading "x_".
Now "x_MailingList" will downconvert correctly to "MailingList".
[SPEC]
- Per the Lancaster Consensus, the 'file' subkey of a package listed in
'provides' must refer to an actual file in the distribution, either the
.pm file that provides the package or another file (*.PL) that
generates it
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.
Changelog:
2.130880 2013-03-29 09:51:00 America/New_York
[BUGFIX]
- Fix provides 'version' bug introduced in the 2.130870 fix
2.130870 2013-03-28 11:08:50 America/New_York
[BUGFIX]
- Don't add 'version' to 'provides' during conversion if one didn't
exist in the original [Reported by Miyagawa; fixed by David Golden]
2.120630 to 2.120921.
pkgsrc changes:
- adjust dependencies
- import split out CPAN::Meta::Requirements into
devel/p5-CPAN-Meta-Requirements
Upstream changes:
2.120921 2012-04-01 15:20:24 Europe/Paris
[REMOVED]
- CPAN::Meta::Requirements has been split out into its own distribution
so it can be used by CPAN.pm without requiring all of CPAN::Meta
2.120920 2012-04-01 11:30:43 Europe/Paris
[ADDED]
- CPAN::Meta::Requirements now has a 'requirements_for_module' method
to retrieve a version requirements string for a specific module
[Leon Timmermans]
[OTHER]
- Parse::CPAN::Meta prerequisite bumped to 1.4403
- JSON::PP prerequisites bumped to 2.27200
- CPAN::Meta::YAML prerequisite bumped to 0.008
2.120900 2012-03-30 13:15:15 Europe/Paris
[BUGFIX]
- CPAN::Meta::Requirements now treats undef requirements given to
from_string_hash() as '0' and warns about it; add_string_requirements()
dies if it does not get a requirements string to parse
2.120351 to 2.120630.
Upstream changes:
2.120630 2012-03-03 14:48:35 EST5EDT
[BUGFIX]
- CPAN::Meta::Requirements now ensures that dotted-decimal versions are
represented in normalized form when stringified. This fixes a
regression in META conversion in 2.120620.
[Reported by Kent Fredric; fixed by David Golden]
2.120620 2012-03-02 12:28:59 EST5EDT
[ADDED]
- CPAN::Meta::Requirements::add_string_requirements allows building
a requirements specification piecemeal [Cory G. Watson]
[BUGFIX]
- Version range handling fixed [rt.cpan.org #75424]
- CPAN::Meta::Converter handles bad version strings more gracefully,
truncating alphanumerics and otherwise falling back to "0". This
is likely better than dropping a prerequisite or dying.
[rt.cpan.org #75427]
2.120530 2012-02-22 16:15:31 EST5EDT
[OTHER]
- Dialed back perl prereq to 5.006
2.112150 to 2.120351.
pkgsrc changes:
- adding dependency to devel/p5-Parse-CPAN-Meta (backend to read
YAML/JSON) by source analyse
Upstream changes:
2.120351 2012-02-03 23:01:45 America/New_York
[OTHER]
- Fixed CPAN packaging errors
2.120350 2012-02-03 22:46:59 America/New_York
[BUGFIX]
- Work around a memory leak bug involving version objects
in boolean context.
2.113640 2011-12-30 15:19:46 America/New_York
[OTHER]
- Version::Requirements has now been merged as CPAN::Meta::Requirements,
rendering Version::Requirements itself redundant
2.112621 2011-09-19 12:15:16 America/New_York
[BUGFIX]
- Spell BACKEND environment variables correctly this time
[noticed by Stevan Little]
2.112620 2011-09-18 20:56:06 America/New_York
[BUGFIX]
- Protect tests against PERL_(YAML|JSON)_BACKEND settings that could
cause tests to fail. (RT #69979)
2.112600 2011-09-17 12:21:09 America/New_York
[DOCUMENTATION]
- Fixed spelling error in CPAN::Meta::Spec (RT #71036) [Gregor Hermann]
2.112580 2011-09-15 10:53:59 America/New_York
[BUGFIX]
- Use UTF-8 mode for internal structure cloning to avoid bugs
in Perl <= 5.8.6 (RT #70936) [Dagfinn Ilmari Mannsåker]
Software distributions released to the CPAN include a META.json
or, for older distributions, META.yml, which describes the
distribution, its contents, and the requirements for building and
installing the distribution. The data structure stored in the
META.json file is described in CPAN::Meta::Spec.
CPAN::Meta provides a simple class to represent this distribution
metadata (or distmeta), along with some helpful methods for
interrogating that data.