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.
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.
in devel/p5-Params-Classify from 0.011nb1 to 0.013
Upstream changes:
version 0.013; 2010-11-16
* bugfix: avoid triggering a core assertion on debugging builds,
by using OP_NULL as a stalking-horse opcode instead of OP_PUSHMARK
(nothing actually broke apart from the assertion)
* provide reserve definition of Newx(), to allow compilation on
non-threaded Perls prior to 5.8.8
* avoid a compiler warning from the reserve implementation of the
ptr_table data structure
version 0.012; 2010-11-03
* generate custom ops for most functions, to avoid heavyweight function
calls at runtime
* change "please update me" messages to "please update Params::Classify"
for clarity
* use shared SVs for return values from scalar_class() and ref_type()
* allow is_able() and check_able() to be called with only one argument
* change message generated by check_strictly_blessed() when called
with only one argument, to be consistent between XS and pure Perl
* refactor some Perl version portability code
* in XS, declare "PROTOTYPES: DISABLE" to prevent automatic generation
of unintended prototypes
* jump through hoops to avoid compiler warnings
* in t/setup_pp.pl, avoid a warning that occurs if XSLoader::load()
is given no arguments, which is now a valid usage
Upstream changes:
version 0.011; 2010-08-21
* bugfix: add a typemap entry for "const char *", to make XS version
of scalar_class() work correctly on Perl 5.6, having been broken by
the const fix in version 0.010
* in XS code, on Perls where it exists (prior to 5.9.5), treat SVt_PVBM
as a scalar referent type
version 0.010; 2010-08-20
* in XS, use PERL_NO_GET_CONTEXT for efficiency
* use full stricture in test suite
* also test POD coverage of pure Perl implementation
* in test suite, make all numeric comparisons against $] stringify it
first, to avoid architecture-dependent problems with floating point
rounding giving it an unexpected numeric value
* make XS code const clean for gcc -Wwrite-strings
* in Build.PL, explicitly set needs_compiler to avoid bogus
auto-dependency on ExtUtils::CBuilder
* in Build.PL, explicitly declare configure-time requirements
* add MYMETA.yml to .cvsignore
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!
This module provides various type-testing functions. These are intended for
functions that, unlike most Perl code, care what type of data they are
operating on. For example, some functions wish to behave differently
depending on the type of their arguments (like overloaded functions in C++).
There are two flavours of function in this module. Functions of the first
flavour only provide type classification, to allow code to discriminate
between argument types. Functions of the second flavour package up the most
common type of type discrimination: checking that an argument is of an
expected type. The functions come in matched pairs, of the two flavours,
and so the type enforcement functions handle only the simplest requirements
for arguments of the types handled by the classification functions.
Enforcement of more complex types may, of course, be built using the
classification functions, or it may be more convenient to use a module
designed for the more complex job, such as Params::Validate.
