Closed dflock closed 1 year ago
What version of eget are you using? I just tried using version 1.3.1 and it worked as expected.
Yeah, latest 1.3.1
Is it possible that at the location eget is trying to extract the binary vale
to there is already a directory called vale
? (Either the current directory or your EGET_PATH
if it is set)
If I run this from my home directory, there is a value folder there already and it fails - if I run it somewhere else where there isn't, it works. However - this is what my config looks like:
➜ cat ~/.config/eget/eget.toml
[global]
target = "~/bin"
upgrade_only = true
So, running it from my home directory fails because there's already a vale
folder there - even through it's supposed to be putting the download into "~/bin"
?
If I run this from my home directory (where there's already a vale folder) eget errata-ai/vale --asset 64-bit.tar --to ~/bin
it works as expected and happily puts vale
into ~/bin
.
So, it looks like my config file isn't working, for some reason? (I didn't notice this initially because I happened to be running eget from ~/bin
).
Ah, putting the eget configuration in ~/.config/eget/eget.toml
(on the XDG path) is a feature that has been added since v1.3.1. For version 1.3.1 you should use ~/.eget.toml
. I will release a new version shortly.
When I run
eget errata-ai/vale --asset 64-bit.tar
I get this:However, if I download that file manually and unpack it, I get this:
It looks to me like that tar file contain
vale
a 15 mb binary. Not sure why eget thinks it's a folder?