Nick Logan
Nick Logan
However a command that outputs all the plugins and if their ‘probe’ status is true would be viable.
zef already notifies you of the possible backend missing in such a scenario
``` Enabled fetching backends [git path curl wget] don't understand $foobar ``` ``` You may need to configure one of the following backends, or install its underlying software - [git...
That wording only makes sense for those specific backend. It doesn’t make sense for e.g. the powershell or perl based backends. The error message only tells us the adapter itself...
And those backends aren’t needed by zef... someone else might have written a different curl backend (which is actually the case)
> On my experience we have so many cases when git is not installed and this why zef could not install git based Raku modules which for the moment quite...
Everywhere else uses `say "===> ..."` so from that aspect it makes sense to get rid of that `note`. I used note in this case though so users could get/pipe...
> I'm not grokking the reasoning behind this. Surely if the CURS doesn't have a module matching the dependency spec, surely the CURI one should be returned if available? How...
> Comments ? Suggestions? I think that is the gist of it other than handling `api` sorting.
> Added api sorting. Having said that, I still think we should disallow distributions with the same ver but a different api (which would make sorting on api not necessary)....