On 8/18/2024 1:56 PM, ASSI via Cygwin-apps wrote:
I'm going to release Perl 5.40.0 to Cygwin in a few days. I've skipped
5.38 in order to update only every second year (which I've done since
the 5.22 release). I haven't seen any trouble in my own Perl
distribution packages from the update even though there are lots of them
that haven't been updated since at least 5.22. So I hope it will be
smooth sailing for anything else depending on Perl also.
Any maintainer having packages that depend on perl5_036 or below should
re-release or upgrade these soon-ish after the Perl update is available,
as otherwise users are either blocked from upgrading Perl or will have
to uninstall the affected packages. The rebuilt packages need to have a
dependency on perl5_040, which cygport provides automatically when
building with the new Perl.
Packages that need an update from perl5_036 are:
biber
nginx-mod_http_perl
perl-Barcode-ZBar
perl-Chemistry-OpenBabel
perl-clinkgrammar
perl-Graphics-Magick
perl-gv
perl-Image-Magick
perl-marisa
perl-ming
perl-Net-Libproxy
perl-net-snmp
perl-openwsman
perl-solv
perl-Stow
perl-Wx-build
perl-Xfce4-Xfconf
perl-zinnia
po4a
subversion-perl
texinfo also depends on perl5_036. It is particularly problematic
because cygport and automake both depend on texinfo (indirectly in the
case of automake). But setup will balk at updating perl as long as
texinfo is installed, making it difficult to rebuild texinfo against the
new perl.
The last time around I dealt with this by forcibly updating perl,
ignoring setup's warnings, and then rebuilding texinfo. See
https://cygwin.com/pipermail/cygwin-apps/2023-May/042902.html
and the followup by Jon. I guess I'll have to do that again unless
someone has a better idea.
Ken
