{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
1.003003 - 2014-12-06
- ensure an old Cpanel::JSON::XS is upgraded if it is too old, as it will
always be used in preference to JSON::XS
- avoid "JSON::XS::Boolean::* redefined" warnings caused by an old JSON::XS
loaded at the same time as a newer Cpanel::JSON::XS
- correctly fix boolean interoperability with older Cpanel::JSON::MaybeXS
1.003001 - 2014-11-13
- fix boolean interoperability with older Cpanel::JSON::MaybeXS
1.003_000 - 2014-10-30
- add :legacy tag to support legacy apps
1.002006 - 2014-10-22
- add some additional test diagnostics, to help find bad version combinations
of JSON backends
1.002005 - 2014-10-12
- fix "can I haz XS?" logic precedence in Makefile.PL
- added the ':all' export tag
- removed dependency on Safe::Isa
- repository moved to git://git.shadowcat.co.uk/p5sagit/JSON-MaybeXS.git
1.002004 - 2014-10-11
- support use of PUREPERL_ONLY in Makefile.PL to avoid adding an XS
dependency
- new is_bool() interface
1.002003 - 2014-10-07
- document how to use booleans
- more metadata fiddling, to remove the Cpanel::JSON::XS dependency visible
to static analyzers (the prequisites at install time remain unchanged)
- fix installation on older perls with an older ExtUtils::MakeMaker
(RT#94964)
- Now also supports JSON::XS, when available: Cpanel::JSON::XS will only be
installed when there is no XS backend already installed; Cpanel::JSON::XS
will be used over JSON::XS when both are installed.
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.
