We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I use custom installation paths for the packages, but when I upgrade them, they are reverted to the default installation path.
Desired behavior would be the package manager realizes the software is installed in a custom directory and then use it for the upgrade.
Thanks for your work!
The text was updated successfully, but these errors were encountered:
Uses installed directory on upgrade.
17482dd
Fixes #15
I don't use this feature very often, so I wasn't aware of this bug, but it seems to be easy to fix.
Can you try with this binary? It should work as expected. hub.zip
Sorry, something went wrong.
I just tried it and now it is working as expected. Thank you for fixing it so quickly! :D
Successfully merging a pull request may close this issue.
I use custom installation paths for the packages, but when I upgrade them, they are reverted to the default installation path.
Desired behavior would be the package manager realizes the software is installed in a custom directory and then use it for the upgrade.
Thanks for your work!
The text was updated successfully, but these errors were encountered: