Closed Dialga closed 2 months ago
Yeah, this seems to be because the shell is not expanding ~
to $HOME, but passing ~
literally to eget
It works for me if you ditch the =
and use eget svenstaro/miniserve --to ~/bin
Is there a way for go to expand paths?
Something like this could work: https://stackoverflow.com/a/17617721
But, I don't really think this is high value, because such expansions should ideally be handled by the shell.
We already have the internal home
package to do this kind of expansion, but I agree I am not sure if we should just leave this to the shell to expand. I guess given that doing the expansion is easy maybe it is worth doing for the to=…
case.
For example I tried
eget svenstaro/miniserve --to=~/bin
expecting miniserve to be installed into thebin
folder in $HOME but rather it created a~
folder in the current directory and renamed miniserve to bin. This is not expected at all since help specifies:--to= move to given location after extracting
. meaning move the executable to that folder.