The Future of the Standard Perl Library
Two schools of thought are battling for the future of the Standard Perl Library. One school would like to have as much as possible in the Standard Perl Library, so they can create applications using the modules they like and be able to distribute them easily without requiring people to install additional modules. The other school wants a minimal distribution with just the right number of modules to allow the later installation from CPAN of additional modules.
Each school has merit. A bigger Library benefits users. They don’t have to bother their system administrators and lawyers to allow them to install additional modules once they have Perl. A smaller library makes it easier for the Perl 5 Porters, who have less of a distraction handling modules and can spend more time working on other tasks.
Some modules are dual-lived, meaning they have two tracks of development. One is in the Perl repository itself and the other is on CPAN. This allows the modules to patch problems more quickly than the Perl release cycle. When it’s time for a new release of Perl, the maintainers merge the changes from the CPAN version into the Perl sources. Sometimes the version in the Perl repository gets fixed first. In that case, the CPAN developers merge the changes at their leisure.
For many years, this process was cumbersome because the layout of the CPAN version and the Standard Library version was very different, making the merge a tedious, hard-to-automate process. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access