-
Notifications
You must be signed in to change notification settings - Fork 140
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
Proper way to update via scoop or clink update? #615
Comments
This is something about scoop, which is interfering with Clink. Specific details follow:
Specifically how did install clink via scoop? I tried it just now, and scoop installed it in I tried
The problem is that somehow scoop has gotten into an unusual state where it's putting the version number in the directory name. That breaks installing for AutoRun, since installing for AutoRun has to use the full pathname, which then gets invalidated with each new version. How did scoop come to put the version number in the directory name? That's something about scoop, not about Clink. |
I figured out what's going on: You ran Injecting Clink defines an alias
So, at this point, then simplest thing is just run (And I'll try to see if there's anything Clink can do to compensate for what scoop is doing, but no guarantees since Clink has no control over scoop.) |
Scoop tries to control app versions and updates. But it makes assumptions which are inaccurate for some apps (such as Clink). Fine. Clink will try to work around that by getting the path that was used to invoke Clink, rather than the path where Clink actually exists. This ends up getting scoop's "current" directory symlink for the app, instead of the real "version" directory of the app. It looks like this shouldn't cause any regressions. Related to issue #615.
I believe I found a way to compensate for what scoop is doing, so that the |
Thanks for the workaround.
|
(Step 3 by itself is the key. The other steps weren't needed.) |
Actually I've tried that step separetly previously. Didnt help. Unless I must run it as a full path, not just |
Yes. I said you have to run it as the full exact path. Literally run Running something else, such as |
So I installed clink via scoop.
now with each new version I do the following:
> scoop update
> clink update
Then when I type
clink info
, the version does show the latest, but this version does not match the value ofbinaries
or thescripts
. It also shows an "old" version in theclink autorun show
.Example where version is 1.6.5, and other values are 1.6.3:
and:
What is the "correct" way to update?
The text was updated successfully, but these errors were encountered: