Front page | perl.perl5.porters |
Postings from February 2017
On 02/08/2017 08:28 PM, Todd Rinaldo via RT wrote: > On Wed, 08 Feb 2017 03:02:39 -0800, xsawyerx@gmail.com wrote: >> Including Module::Install *does* implicitly encourage it. The only way >> would be to document very very clearly that it should not be used. At >> the same time, this also implies an adoption of this by p5p, even if >> to slowly deprecate it. >> >> This raises another question on my part: Is the intention for this to >> be for good, or for a period? If for a period, how long of a period? > So the very ROUGH numbers I have are that ~3900 out of 35,000 modules on CPAN use Module::Install. That's ~11% of CPAN. I'm not optimistic even Karen could get patched or adopt that many modules. This would probably be with us for some time. I got this by putting all of minicpan into a git repo and I know there are a few dupes. https://github.com/toddr/minicpan_grep > > After talking with toolchain, the below idea has been floated. It would allow us to ship ONLY this one file and not M::I with Perl. We could add docs, warnings, etc. to make it clear this is a shim ONLY for working around Module::Install's incompatibility with . not being in @INC. > > https://gist.github.com/toddr/a0d877645575df5615cff30fcaf379ad Considering this has been discussed exhaustively with toolchain, despite the icky feeling that comes with it[1], I support this solution. I have confidence and trust in toolchain's suggestion. I would like to know if anyone objects to this. If not, we should include it soon for 5.25.10. [1] Shared by all included in the debate around it, as far as I've seen. :)Thread Previous | Thread Next