Open lstep opened 9 years ago
Here's a guide for forking a git repo and fetching updates from upstream -- in this case, the original GVM repo.
@remy-actual If it was just a git update, I wouldn't open an issue. From what I see in the binscripts/gvm-installer
file, it's unfortunately much more than that...
@lstep Sorry, I wasn't specific:
Forking the GVM repo, and editing line 48 of gvm-installer
from SRC_REPO=${SRC_REPO:-https://github.com/moovweb/gvm.git}
to SRC_REPO=${SRC_REPO:-https://github.com/YOUR_GITHUB_ACCOUNT/gvm.git}
means running the forked gvm-installer script will install locally from the forked repo.
This allows for fetching and merging changes from the upstream gvm repo without overwriting your local pkgsets.
Obviously this isn't a fix for the issue -- presenting this as a workaround you or others may find useful in the interim.
:+1: for adding a gvm update command (with documentation).
EDIT: Have you tried $gvm get
?
Looks like that is the upgrade command you are looking for: gvm/scripts/get.
rename gvm get
to gvm upgrade
in cmd usage will avoid such confusion.
I think I'll leave get in place for backwards compatibility but add upgrade as an alias to get and update the readme.md with upgrade instructions. Perhaps have gvm give a message when an upgrade is available.
There is no information on how to upgrade gvm. Is it even possible to upgrade without reinstalling everything (rm -rf ~/.gvm)? I have several pkgsets I don't want to loose.