Re^4: Why don't some CPAN modules append perllocal?

It's hard to believe that a bug in a popular CPAN module can be considered "low priority" and not fixed since 2005, when this bug destroys and renders inconsistent Perl's simple mechanism for recording module installation history. Without perllocal you have to traverse @INC and stat every module file to figure out when they were installed. If a module was edited or something then it becomes very difficult to impossible to tell when it was installed. Is this information stored anywhere else, does the cpan utility keep track of what it has done?

Comment on Re^4: Why don't some CPAN modules append perllocal?

Replies are listed 'Best First'.
Re^5: Why don't some CPAN modules append perllocal? by hv (Prior) on Jan 29, 2023 at 19:54 UTC
As far as I have ever been able to tell, the original developers and subsequent maintainers of Module::Build have always considered this more a wishlist item than a bug. But as far as I know nobody has cared enough to submit a pull request; it seems at least possible that it would be applied.	[reply]
Re^6: Why don't some CPAN modules append perllocal? by LanX (Saint) on Jan 29, 2023 at 20:27 UTC
I couldn't find any "official" documentation for `perllocal` and I doubt there is any standard, since naming it so closely to `perllocale` would be more than unfortunate. If it's a pseudo-standard by some installers/builders, than the next question is, if such a limited static list in POD is a better choice over searching @INC dynamically. Hence what's the use-case? I have some ideas about that, but most of them would be better covered by cpan and cpanm creating something like YAML or JSON. Cheers Rolf _{(addicted to the 𐍀𐌴𐍂𐌻 Programming Language :) Wikisyntax for the Monastery}	[reply]