@Htbaa @Perl @miyagawa
• cpanm --with-feature is considered experimental https://metacpan.org/dist/App-cpanminus/view/lib/App/cpanminus/fatscript.pm#-with-feature,-without-feature,-with-all-features
• The #cpanfile feature directive is modeled after the #CPAN metadata spec’s optional_features map, whose documentation discourages its use because a reverse dependency has no way to specify which features its dependent distributions should enable. https://metacpan.org/pod/CPAN::Meta::Spec#optional_features
• The point of #Carmel seems to be to produce repeatable builds. Providing feature switches to cpanm sounds counter to that.
cpanm

get, unpack build and install modules from CPAN

MetaCPAN

Having always used #cpanm with #perl I'm now looking into #Carmel and find it an interesting concept. However, with cpanm and a #cpanfile I can declare a feature which include dependencies that are only installed when I pass the flag to cpanm. But it seems this isn't possible to do with Carmel?

@Perl