FWIW this isn't a simple bump, it requires rebuilding every Perl package in the repo

In D299#4303, @ikey wrote:

FWIW this isn't a simple bump, it requires rebuilding every Perl package in the repo

I know, that's why I added the Requires Rebuilds tag (but I have no clue how many packages are impacted)
As usual, I drop this here so it's available if/when you need it, but if you think it's too much work for too few benefits, just abandon it !

No no - we're not avoiding updates cuz its easy :P It'll need to wait until post-sync though

Fixes T3828

I wouldn't do this till at least after ferryd... It was about 120 packages last time (took a whole day waiting for eopkgs to filter through) and will be even more now. Though creating some form of system to do python and Perl upgrades will be pretty essential if we want to update Perl every point release

In D299#29635, @sunnyflunk wrote:

Use 5.26 for version so each point release doesn't require full rebuilds

Here is a nice tip I used in some other packages to do the same : ${version%.*}

${string%substring} : Deletes shortest match of $substring from back of $string.

https://packages.solus-project.com/shannon/p/ and https://packages.solus-project.com/unstable/p/ show 152 packages with perl in the name.
The unstable link shows 24 of those perl-related packages which still show a 2017 date stamp, so I guess they're almost done rebuilding.

In D299#29709, @mate-user wrote:

The unstable link shows 24 of those perl-related packages which still show a 2017 date stamp, so I guess they're almost done rebuilding.

Are you sure? I saw one and that's now rebuilt (it missed my search criteria as the pspec showed it was last built with perl 5.22.1 (so missed my 5.24.1 scan).

I'll need examples (and go into the directory to check to ensure that you don't have an old cache of the directory page).

@sunnyflunk yes now all of them show 2018.
I counted 24 with the 2017 date a few minutes before posting that comment yesterday 17th Jan at 2:19am haha!