NAME<\/a> List::MoreUtils::Contributing \u2212 Gives rough introduction into contributing to List::MoreUtils<\/p>\n List::Moreutils has a turbulent history and a strong approach. Before going further, please step to Open Source Contribution Etiquette The current distribution is a balance between finishing the history and claiming for future requirements. Therefore some components will receive a rewrite on purpose \u2212 others won\u2019t.<\/p>\n For the moment \u2212 it\u2019s not the primary goal to clean up the configuration stage, until the primary goals and prerequisites are done.<\/p>\n To contribute to List::MoreUtils, one has to arrange with the current situation, dig into details and ask for clarifying when parts are incomprehensible.<\/p>\n Primary Goals<\/b> As example see RT#93207 or RT#75672 for missing configure time checks, while RT#93207 radiates until test \u2212 but doesn\u2019t affect runtime nor installation (beside test failures).<\/p>\n Secondary Goals<\/b> One example of removing unnecessary infrastructure could be to move Data::Tumbler and Test::WriteVariants into authoring mode, when improved test for RT#93207 could be reasonably done by a module which is recommended for test. The recommendation of Graham Knop\u2019s Makefile.PL#L82 Orientation Guide<\/b> The reason for Config::AutoConf is quite simple \u2212 the opportunities for checking the environment cover a much wider range than a simple test whether there is a working compiler. It requires a lot of improvements since its base ExtUtils::CBuilder was never designed to support that kind of solutions \u2212 but there is Work In Progress<\/i>. To finally solve issues as RT#75672 even in cross-compile environments \u2212 there is no way around such a checking tool.<\/p>\n The reason for Data::Tumbler in combination with Test::WriteVariants are extensible tests with reasonable effort and easy figuring out which extra condition causes failures. Also \u2212 missing pre-conditions should result in failing tests i some cases \u2212 what is fully supported by the logic behind Data::Tumbler in combination with Test::WriteVariants.<\/p>\n Finally \u2212 inc::latest glues the stuff in a bundle together to allow people with older toolchains to use List::MoreUtils out of the box (maybe with reduced quantity but full quality).<\/p>\n Config::AutoConf, Data::Tumbler, Test::WriteVariants, ExtUtils::MakeMaker::Extensions<\/p>\n
DESCRIPTION<\/a>
SEE ALSO<\/a>
AUTHOR<\/a>
COPYRIGHT AND LICENSE<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
The very first primary goal is to clear the backlog. These are primarily the open issues, feature requests and missing infrastructure elements.<\/p>\n
Secondary goals are harmonizing the function names and calling convention (see RT#102673), tidying the infrastructure of the distribution and remove unnecessary complexity (while protecting the necessary).<\/p>\n
List::MoreUtils configuration stage heavily depends on Config::AutoConf and Data::Tumbler. A few prerequisites of both modules aren\u2019t available for Perl 5.6 \u2212 which leads to a tiny emulation layer t the begin of “Makefile.PL”.<\/p>\nSEE ALSO <\/a> <\/h2>\n
AUTHOR <\/a> <\/h2>\n