If you have a Perl-related news item you'd like to share, you may post it in the Perl Newssection.
Please try to avoid duplicating news; but pointers (with summaries) to important stories on other sites are acceptable here.
The Perl Foundation (TPF) exists to support the Perl community and all the people within our community, including the newly renamed Raku;
the name change doesn’t alter the nature of our involvement or support with Raku.
The Grants Committee will continue to accept grant proposals for Perl 5, Raku, and other Perl-family projects work as before.
TPF will continue to encourage development of Perl and Raku events, workshops and hackathons and generally support the global communities.
The Perl Conference (TPC) will also continue to accept presentation proposals for all Perl-family languages, including Perl 5 and Raku.
The new features are pretty minor. Most of the improvements are in documentation and testing.
Totally rewritten manual/tutorial.
Every issue on RT has been handled.
Bigger test suite. The exact number of tests run varies based on the availability of optional dependencies, but I just ran the test suite with EXTENDED_TESTING set to false and most of the optional dependencies installed, and it was nearly 7500 tests, compared to just over 2700 for Type::Tiny 1.6.0. With EXTENDED_TESTING true, there are nearly 13900 tests.
The official Perl documentation site at https://perldoc.perl.org was recently overhauled. Independently, I put together a reimagined documentation site that would be hosted at https://perldoc.pl. In the interest of providing a documentation site that best serves the needs of the Perl community, we need your feedback. Please give both sites a try, in-depth if you want, or just how you would most commonly use the site. What do you like about the design or the functionality of each site? What is missing or can be improved? Any feedback regarding what you want from the Perl documentation site is helpful and appreciated. Please leave comments here or in the linked posts by Monday Nov 18th.
I am in favor of this change, because it reflects an ancient wisdom:
“No one sews a patch of unshrunk cloth on an old garment, for the patch will pull away from the garment, making the tear worse. Neither do people pour new wine into old wineskins. If they do, the skins will burst; the wine will run out and the wineskins will be ruined. No, they pour new wine into new wineskins, and both are preserved.”
"CPAN is wonderful and it is vast. Task::Kensho offers a curated look at the best it has to offer for those who don't know what to look for. But to remain useful, it must keep up with the trends of CPAN and the community. Thus, the community's input is vital to its maintenance.
"Please, take a moment and look through the open issues. Comment or add a reaction in support of changes that make sense to you, and open a new issue if you think something is missing."
See my blog post for more information, and an example of the new berrybrew virtual command.
Here's a summary of the new features:
berrybrew virtual allows you to manage non-Strawberry external Perls
Unattended installations now possible
new quick argument to berrybrew switch allows switching to new Perl instances without opening a new CLI window
berrybrew module export and berrybrew modules import allows you to export and import modules between Perls. Custom module list files allowed
Ability to change between Strawberry's home directory and Windows home directory when using File::HomeDir
Management of external Perl installations; Using the new berrybrew virtual command, one can bring in other installations of Perl for management under berrybrew. For example, if you have an ActiveState Perl installed on the system, you can virtualize it under berrybrew, and use or switch to it just like any of the portable Strawberry Perls we normally manage. This means that you can switch over to your system Perl when needed, without having to modify PATH, or temporarily disabling berrybrew
Unattended installations are now possible. We no longer prompt for user acceptance when running the initial configuration
New quick argument to berrybrew switch; This allows you to switch to a different Perl instance persistently without having to close the existing CLI window and opening a new one (note: some binaries and features may not work correctly. If you run into problems, simply open a new window)
Export and import modules from one Perl instance to another; berrybrew modules export and berrybrew modules import will dump a list of all installed CPAN distribution names from one Perl and install it on others. The export files can be edited at will before re-importing, and you can even create your own module list files to use as you see fit. Using this feature, in conjunction with berrybrew clone allows you to easily set up template Perl instances for very quick Perl platform setup
Ability to change the location where File::HomeDir points to; you can switch between the Windows home directory location, or the default location that Strawberry Portable editions set
Side note... a request came in by a user to support previously installed Perls. Their developers use berrybrew, but all of their CI happens automatically on a locally installed Active State Perl. They wanted a way to be able to use Active State for their testing pipeline, without having to muck with path environment variables and such that would mess up the developer environment. With berrybrew use virtual_instance, the system Perl can be used for the CI runs without affecting the rest of the system.