Module-Pluggable
Module-Pluggable copied to clipboard
simonwistow
Automatically give your Perl module the ability to have plugins
Callers of Module::Pluggable may fail with perl 5.34 on Windows (for example Perl::Critic - but possibly some more modules and tests). This is caused by the (undocumented) changed default behavior...
https://metacpan.org/release/Module-Pluggable/ says that latest is 5.2 but here is missing git tag for that version.
If you have Foo/Bar.pm and even look at it on a Mac it will create Foo/.AppleDouble/Bar.pm, which is some binary nonsense and definitely not a module. This little patch makes...
Installation on this env: - OS: Darwin OSTML0244651 16.7.0 Darwin Kernel Version 16.7.0 - Perl: 5.26.0 (via perlbrew) Installation of module Module::Pluggable v5.2.2. fails: 1) Requirement Font::TTF seems missing from...
The "P" should be capitalized: ``` diff --git a/Makefile.PL b/Makefile.PL index ed13fa2..81b5eda 100644 --- a/Makefile.PL +++ b/Makefile.PL @@ -86,7 +86,7 @@ my %WriteMakefileArgs = ( }, test => { suggests...
See https://github.com/github/gitignore/blob/master/Global/Vim.gitignore and http://vimdoc.sourceforge.net/htmldoc/recover.html#swap-file
This enables a poor man's authorization of plugins on file system basis. E.g., MooX::Cmd uses this module to discover subcommands. Withdrawing read permission on files enables allowing different user groups...
It'd be really nice if max_depth took an arrayref like some of the other arguments. That, or if there was a special no recursion option .... I have a situation...
It's not uncommon to have perl modules installed by root in docker images, especially for one-off, quick tasks. Doing so causes the unreadable files tests to fail in releases 6.1...
Metadata
Owner
Metadata
Automatically give your Perl module the ability to have plugins