Bug #127625 for Keyword-Pluggable: Build problems (1.02)

On 2018-11-11 07:56:13, SREZIC wrote: Show quoted text
Pod::Markdown is specified as a dependency, but I think this does not work in a test-only or test-then-install cpan client setup --- in these setups only PERL5LIB is adjusted for not-yet installed dependencies, but PATH is not.

Hi Slaven Thank for reporting these, I have fixed them in git but won't push the new version yet. As for this ticked, what is it you mean by "test-only or test-then-install cpan client setup" -- or more importantly, do you know how I test for those? /dk

Generating the README.md file only really seems useful for the author, not users of the library. Rather than listing Pod::Markdown as a prerequisite, it would probably make sense to only generate it when in a git checkout rather than an extracted tarball. One way to check if you are in an extracted dist is based on the presence of a META.yml file. ExtUtils::MakeMaker will generate these in the dist as it builds it, but won't place one in the development directory. Something like: sub MY::postamble { return '' if -f 'META.yml'; return <<'POST' pure_all :: README.md README.md : lib/$(subst ::,/,$(NAME)).pm pod2markdown < lib/Keyword/Pluggable.pm > README.md POST }

On 2018-11-13 06:44:51, KARASIK wrote: Show quoted text
* test-only cpan -t Module This is roughly what some smokers do (i.e. never install --- have a minimal perl setup before starting a test). Probably there's something similar for cpanm available. * test-then-install This can be done within the CPAN shell: test Module is_tested install_tested This may be a real workflow for some users: first test the module and all dependencies, and only if everything works, do the installs.