-
-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zef pre-run test #350
Comments
Well those backend are all plugins. For instance no one on Linux cares that powershell is not installed. Additionally the only required backend is the one for handling paths — everything else (tar, git) is extra and depends on the ecosystems you need to use and can’t be determined until runtime when you actually give it a query (it can’t know you need git until it has to look for something and ends up with a git url, which is not always the case). |
However a command that outputs all the plugins and if their ‘probe’ status is true would be viable. |
I think that output from a probe for all plugins would be good. So if zef fails because a plugin fails, there is some more information about which one. Although when I got the info back, I checked unzip and curl. I didn't think to check if I had git. So I went looking elsewhere. |
My suggestion if one tries to install git hosted module and git client is not here, zef will notify it |
zef already notifies you of the possible backend missing in such a scenario |
I see. Does it notify about absence of git client?
…On May 29, 2020 10:18 AM, "Nick Logan" ***@***.***> wrote:
zef already notifies you of the possible backend missing in such a scenario
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#350 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHRHSPMOAJSLFM5BE477TLRT7G3LANCNFSM4NOCTFYQ>
.
|
|
It seems the information is there, but perhaps rewording the message might help.
Perhaps the following
|
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 could not load, which may not even shell out to something so just using stronger wording to suggest what is missing will just make it confusing in a different way. |
And those backends aren’t needed by zef... someone else might have written a different curl backend (which is actually the case) |
hi @ugexe I second @finanalyst option. Irrespective on zef underlying model, is it a big deal for zef to check that git installed or nor not and then just say so? 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 a few. |
right, so maybe that is the issue with git backend? |
or maybe we need to change zef backends API, when plugin might have a |
I mean it literally tells you "You may need to configure one of the following backends, or install its underlying software - [git wget]" as soon as it knows it needs something you don't have to do what you ask. You can install local path modules without curl/wget/etc, and indeed almost every single raku user uses this workflow as the first thing they do |
I am installing Rakudo on a new server, and ran into the backend not configured problem. It took a while to realise that git had not been installed (fresh server).
Suggestion
Would it be possible to have a one-off zef-check option that zef runs the first time that verifies whether software it relies on is present in a system, eg. git, curl, unzip.
A bit like the environment checks that are in a makefile.
These 'environment' softwares are normally available on a developer's system, but not on a fresh server, or one where the intention is to install a minimum number of dependencies.
The text was updated successfully, but these errors were encountered: