You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I delete a package using aqua rm <package-name> and doing command -v <package-name> still shows as ${HOME}/.local/share/aquaproj-aqua/bin/<package-name>. But running <package-name> still works as expected which is falling back to the real path where the aqua unmanaged program is located. It's just a nuisance in my case.
How to reproduce
aqua.yaml
Other related code such as local Registry
Executed command and output
$
Debug output
$
Expected behaviour
aqua-proxy symlinked should be removed from the aqua/bin directory.
Actual behaviour
It's still there but it "re-routed" the package to where the aqua unmanaged program is located in $PATH which is good.
Note
No response
The text was updated successfully, but these errors were encountered:
Thank you for your feedback.
This is not a bug but an expected behaviour.
As you said, even if symbolic links are remaining aqua fallback to executable files in PATH.
And you can get paths to them by aqua which command.
We intentionally keep links for lazy install.
I understand your opinion, so one idea is to add a command line option to remove symbolic links.
e.g.
aqua rm --remove-link cli/cli
I don't come up with a good option name. --remove-link is ambiguous if only symbolic links are removed or both symbolic links and executable files are removed.
Thanks for the reply! Didn't know there's aqua which command, pretty neat.
I'm fine with --remove-link, and I can't think of any possibility where you want to remove link and not the executable file? I usually wrong about things though so 😆
aqua info
Overview
I delete a package using
aqua rm <package-name>
and doingcommand -v <package-name>
still shows as${HOME}/.local/share/aquaproj-aqua/bin/<package-name>
. But running<package-name>
still works as expected which is falling back to the real path where the aqua unmanaged program is located. It's just a nuisance in my case.How to reproduce
aqua.yaml
Other related code such as local Registry
Executed command and output
Debug output
Expected behaviour
aqua-proxy
symlinked should be removed from theaqua
/bin
directory.Actual behaviour
It's still there but it "re-routed" the package to where the
aqua
unmanaged program is located in $PATH which is good.Note
No response
The text was updated successfully, but these errors were encountered: