Pumpking email list?

[blue_cowdawg]

Once upon a time many many moons ago <waving hand across sky> I used to belong to an email list that clued the recipient into what CPAN modules had been updated. At some point those emails stopped coming to me and I didn't notice because I had an email filter that obediently filed the emails away in a folder for me to read later.

I find myself once more in my career being the custodian of all things CPAN for my department and would like to start getting those emails so I can track the "latest and greatest" and update our local repository accordingly.

Having done numerous Google searches I can't seem to find where that email list lives or how to get back onto the list. Did the list go away? If not where do I sign up?

Hoping some Monk will have an answer...

[Corion]

Not knowing about such a list, if you already have some RSS-to-email gateway like feeder, you can use the CPAN Uploads RDF to notify you of all releases. I think there also is cpan-outdated, which could keep you abreast of differences between your install-base and the upstream CPAN.

[stevieb]

You might try the cpan-uploads email list. It receives email any time anyone uploads a new distribution (or an existing distribution with a bumped version number). There may be others... you can look through most of the Perl-related email lists here.

Unrelated to your request but on-topic because you mentioned him, the Pumpking (SawyerX) can usually be found hanging around with the Perl 5 Porters.

[blue_cowdawg]

Looks like I need to use RSS. Didn't see any subscription info for a an email list for CPAN uploads. I finally found something Microsoft Outlook is good for. I've plugged the RSS feed into it and voila I got what I'm looking for. :-)

Next will be a Perl script to process the RSS feed and alert on modules I care about.

[hippo]

If you only care about a subset of modules then maybe going directly to https://www.perlmodules.net/ might be simpler? Setting up an RSS feed and/or email alerts on a personally-selected subset of modules is its raison d'etre.

[blue_cowdawg]

I'm still exploring just how I do this. My ultimate goal would be for whatever script I end up writing to open a ticket in whatever ticketing system d'jour they have us work with next when a change to one of the modules in my list happens.