Perl/CPAN people, I haven't received any emails sent to or forwarded from my cpan.org email address for the last month. It seems to be affecting other users as well. Anyone know anything about this? #perl #cpan #perl
@manwar Test2 is great, but whenever I see something using yath on one of my #CPAN testing machines it seems to be incredibly slow. Don't know why, and have better things to do than investigate, but that's put me off using it.

"575 Pull Requests in Three Weeks: What Happens When #AI Meets #CPAN Maintenance"

This is an interesting read, including the comments.

https://blogs.perl.org/users/todd_rinaldo/2026/04/575-pull-requests-in-three-weeks-what-happens-when-ai-meets-cpan-maintenance.html

#Perl #LLM #Claude

575 Pull Requests in Three Weeks: What Happens When AI Meets CPAN Maintenance | Todd Rinaldo [blogs.perl.org]

I've uploaded a new #Perl Critic policy that checks code for naive random data generation from a hash over not-so-randonm sources like rand(), system time, pid such as

md5_hex( rand . time . $$ . ++$counter )

This anti-pattern is used in many places, and has been the reason for several CVEs.

https://metacpan.org/release/RRWO/Perl-Critic-Policy-Security-RandBytesFromHash-v0.1.0

#CPAN #security

As a scholarly aside, I am curious as to who first came up this anti-pattern.

Client Challenge

A new blog post on the nature of #CPAN-based experiments at adding new syntax and features to the #Perl language.

Or at least, the first half before I get around to writing the thing I was actually going to say, in likely a follow-up post next week.

https://leonerds-code.blogspot.com/2026/03/cpan-based-experiments-reminder.html

CPAN-based Experiments: A Reminder

I've been adding new features to core perl for a number of years. For the most part, all of the big things I've been adding have been near-c...

Gonna build a #CPAN testing VM with #DragonflyBSD. Any gotchas that my fedihomies think that a seasoned Unixhead should know about?

#perl

A few days ago I tried to build some perls with 32 bit ints and 128 bit floats. Cue test failures. Today I tried again, and this time I read my notes from last time on how to do it, and it Just Works.

Yay past me!

(the #BigInt modules bundled with some versions of perl don't like that combination of data sizes; the solution is to ignore their test failures, install anyway, and then upgrade to the latest versions from the #CPAN)

#perl #32bit #RidiculousComputing #ComputationalPerversions

I have released a new version of App::CpanDak, my sub-class of App::cpanminus / cpanm with "some sort of distroprefs"

You could already apply patches, skip tests, and set environment variables, to any distribution you installed; now you can augment version specifications.

Some::Fancy::Library has released a new version 1.3.4 that doesn't install cleanly? add a Some-Fancy-Library.options.yml with:

--- add_version_spec: "!= 1.3.4"and that version will be skipped, even if pulled in via indirect dependencies!

https://metacpan.org/release/DAKKAR/App-CpanDak-0.1.0

#perl #cpan

App-CpanDak-0.1.0

cpanm, with some sort of distroprefs

MetaCPAN
Client Challenge

Hm, did Data::Random got deleted from #CPAN? I have some failing build pipelines and metacpan does not list it anymore, only some dependencies. #Perl Anybody knows who can investigate this?