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.
Changes from previous:
0.28 Thu Jul 08 20:30:00 CEST 2010
===================================
* Upgrade the plugin for Catalyt 5.8 series
* Changes for adopting MRO::compat where not complete. Calls to next::method
instead of NEXT::...()
* Change name of paths and compiled base class properties in Cat 5.8
* Clone the result before serializing, as RPC::XML won't clone already seen
refs (thanks t0m)
* Fix the test suite (some tests were lost from 0.24->0.26)
* Don't warn about the breakage of XML::RPC, as the author has already
fixed the backcompat breakage
0.26 Fri Sep 25 13:50:41 CEST 2009
===================================
* Important notice: RPC::XML 0.69 introduced a backwards incompatible
change. For now, this module will only work with RPC::XML 0.67 or
before. See this bug report for RPC::XML for details:
https://rt.cpan.org/Ticket/Display.html?id=50013
* Address: #44995: Instruction to disable RenderView action.
Updated tutorial accordingly.
* Address: #46316: Catalyst::Plugin::Server is trying to use NEXT, which
is deprecated. We are now using MRO::compat instead.
* Address: #45709 Documentation Ambiguity leads to confusion; The use of
$c->req->xmlrpc->error is now documented in more detail.
* Add unicode tests
* Other small test improvements
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!
Base plugin for XMLRPC and SOAP server.
XMLRPC Plugin for Catalyst which we tried to make compatible with
the way Catalyst works with URLS. Main features are:
* Split XMLRPC methodNames by STRING to find out Controller.
* Single entrypoint for XMLRPC calls, like http://host.tld/rpc
* DispatchTypes (attributes) which work much the same as Catalyst attrs
* XMLRPC Parameter handling transparent to Catalyst parameter handling
