miyagawa
commented
1 year ago I can reproduce with for example MooseX::XSConstructor, MooX::XSAccessor
These two modules do not exist on CPAN, perhaps typos?
I did the guess work and tried it with MooseX::XSAccessor, and it seems to work fine:
➜ cat cpanfile
requires 'MooseX::XSAccessor';
➜ carmel install
Using MooseX::XSAccessor (0.009)
Using Class::XSAccessor (1.19)
Using Moose (2.2201)
Using Class::Load (0.25)
Using Data::OptList (0.112)
Using List::Util (1.63)
Using Params::Util (1.102)
Using Sub::Install (0.928)
Using Module::Implementation (0.09)
Using Module::Runtime (0.016)
Using Module::Build (0.4231)
Using Try::Tiny (0.31)
Using Package::Stash (0.40)
Using Dist::CheckConflicts (0.11)
Using Package::Stash::XS (0.30)
Using Class::Load::XS (0.10)
Using Devel::GlobalDestruction (0.14)
Using Sub::Exporter::Progressive (0.001013)
Using Devel::OverloadInfo (0.007)
Using MRO::Compat (0.15)
Using Devel::StackTrace (2.04)
Using Eval::Closure (0.14)
Using Module::Runtime::Conflicts (0.003)
Using Package::DeprecationManager (0.17)
Using Sub::Name (0.26)
Using Sub::Exporter (0.988)
---> Complete! 1 cpanfile dependencies. 26 modules installed.
➜ carmel exec perl -e 'use MooseX::XSAccessor (); warn MooseX::XSAccessor->VERSION'
0.009 at -e line 1.
bbrtj
Can't find any documentation on it, so I'll assume it's a bug:
I can reproduce with for example MooseX::XSConstructor, MooX::XSAccessor, but not with Path::Tiny:
Same with
use Carmel::Setupinside the script. Modules are loadable before that statement, but not after.