Kang-min Liu

Evidently `perlbrew list-modules` does not show "core modules" in the output. Usually after switching to a newly installed perl, rurning `perlbrew list-modules` produce no output. While `Archive::Tar` is already installed...

Thanks for reporting, It looks like the file modes in the tarball for 0.83 are not preserved. I migrated the CPAN authoring tool to `mbtiny` and it is most likely...

Thanks @KES777 , but previously, using `env perl` to run perlbrew itself created some some known issues, mostly when loading core, XS-based modules, namely `Cwd`. Thought I havn't re-visit this...

Both `clone-modules` and `list-modules` command are just using `ExtUtils::Install`, which is looking up information based on the exstence of `.packlist` files that does not presever the original distribiton name. We...

Looks like @skaji has already did some work in this part: https://metacpan.org/pod/Distribution::Metadata

This will be fun... the "receipt" of LWP looks is this: ``` # cat darwin-2level/.meta/libwww-perl-6.52/install.json | jq { "provides": { "LWP::Protocol::nogo": { "version": "6.52", "file": "lib/LWP/Protocol/nogo.pm" }, "LWP::Protocol::data": { "file":...

I give this a bit of thoughts and it now seems to me that, for the scope of perlbrew the sensible solution is to make `list-modules` and `clone-modules` do some...

@karenetheridge Because that is how `ExtUtils::Installed` reported... currently the list of "modules" obtained by doing this: perl -MExtUtils::Installed -E 'say for ExtUtils::Installed->modules' I guess the definiton of "modules" might be...

Perhaps this should be part of patchperl.

@doy, I like simplicity over explicitly. This command syntax can only be ambiguous if the installation name (or alias) contains commas, or is the same as one of perlbrew command:...