PDL 2.038

[Sebastiaan Couwenberg]

On 4/21/21 6:45 AM, Ed . wrote:
> I’ve recently updated PDL::LinearAlgebra, PDL::Stats, and PDL::FFTW3 to leverage the new native complex features, which are already making dealing with complex numbers (very important in physics applications) much easier to deal with (no spurious extra dimension of 2 to confuse things, functioning transposes, etc). Since this revealed various either bugs or features needed in PDL, that’s been getting updated frequently.
> 
> I’m a bit surprised that not all the PDL modules that I’ve released recently got a mention. Am I correct that Debian covers all CPAN PDL modules, or are there some it doesn’t?

Only a subset of CPAN is packaged. For the PDL ecosystem we have
packages for:

 * PDL (pdl)
   Recently updated.

 * PDL::CCS (libpdl-ccs-perl)
   Last upstream release in November 2020.

 * PDL::Graphics::Gnuplot (libpdl-graphics-gnuplot-perl)
   Recently updated.

 * PDL::IO::HDF5 (libpdl-io-hdf5-perl)
   Last upstream release in June 2015.

 * PDL::IO::Matlab (libpdl-io-matlab-perl)
   Last upstream release in December 2012.

 * PDL::LinearAlgebra (libpdl-linearalgebra-perl)
   Recently updated.

 * PDL::NetCDF (libpdl-netcdf-perl)
   Last upstream release in November 2013.

 * PDL::Stats (libpdl-stats-perl)
   Recently updated.

 * PDL::VectorValued (libpdl-vectorvalued-perl)
   Recently updated.

 * TFBS (libtfbs-perl)
   Last upstream release in March 2017.

> Also, in PDL itself, we’ve been rearranging things like bringing all the GSL modules in one place, and making pthreads work much more widely, and fixing the Proj.4 modules. Rather than sit on these changes, like in years past, for many months, we’ve been releasing them. If this causes actual problems for the state of libpdl-*-perl, I’m asking what problems, so that we can come up with solutions. They say in agile development circles that if releasing code is painful, you should do it more often. It’s the PDL project’s aim that every commit that passes CI could be released (though obviously that will never be literally done). Let’s catch problems earlier or actually automate everything, so it’s all smooth.

PROJ is actually the primary reason I got involved with maintaining the
pdl package in Debian as I'm the maintainer of the proj package (among
many other GIS packages like netcdf) in Debian.

Support for modern PROJ is still lacking, Alien::Proj4 doesn't support
it either. But at least it PDL got updated a while ago to gracefully
disable the PROJ support when building with modern PROJ instead of failing.

The recent core_version bump to 13 will require a rebuild of all pdl
reverse depenedencies in Debian, some of those who have not recently
been updated are expected to fail. Because Debian is currently frozen in
preparation of bullseye stable release I haven't bothered to prepare
this transition yet, so no test rebuilds have been preformed yet. That
will happen after the bullseye release.

> Alternatively, you’re welcome to only sip from the firehose and not process more than one release a month. That’s also cool!

We'll see how it goes after the bullseye release.

Note that I only maintain the pdl package and its reverse dependencies
to not block my work on the GIS packages, I don't use any of them myself.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1