On Tue, 27 May 2014 23:56:03 +0300, Niko Tyni wrote:
> (Hm, my preliminary testing indicates that 5.20.0 may introduce new
> challenges around PERL_DL_NONLAZY. Urgh. Will investigate.)
Today while reading
https://metacpan.org/pod/distribution/perl/pod/perldelta.pod#Module-removals
I remembered/detected 2 small challenges as well:
- CGI and friends are removed; CGI.pm is already packages separately
anway; where it gets interesting is that CGI::Fast, which was also
part of perl core,
+ is split off into its own dist since CGI 4.0
+ but is currently also in its own binary package libcgi-fast-perl,
produced by the perl source package
so we can't just package the new separate CGI::Fast as
libcgi-fast-perl.
I guess waiting for 5.20 (which probably will drop the libcgi-fast-perl
binary package) and making a somehow coordinated upload of
libcgi-pm-perl 4 (without CGI::Fast) and a new separate
libcgi-fast-perl should be enough? (With getting versions right et
al.)
- The other interesting point is Module::Build; in the regard that we
have tons of "Build-Depends: libmodule-build-perl (>= 0.nnnnnn) |
perl (>= 5.1x.y)" which will (not fail with sbuild which picks the
first alternative) be wrong and cause build failures with
p/cowbuilder, once 5.20 without M::B fulfills the second
alternative. - Oh, but the opposite order might fail? Or not, if
perl 5.20 depends on libmodule-build-perl?
Sounds like a nice mass-commit (or even upload)?
But before that we should agree on what we'll use instead; and I'm
not sure that Config::Model::Dpkg will do the right thing here ...
(libmodule-corelist-perl is already up to date).
Dominique?
Just some half-baked thoughts before I forget them :)
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
`- NP: hons: molly is ashes (1)
Attachment:
signature.asc
Description: Digital Signature