Ability to self update releases zip install

[mavwolverine]

If I download a release from github, extract it to ~/.antidote (or someplace else and link it), antidote update says use package manager since it is not a git version.

https://github.com/mattmc3/antidote/blob/main/functions/antidote-update#L90

Somehow it should figure out if it was installed using package manager or directly. If directly it should download from github releases and replace the files.

[mavwolverine]

Some initial thoughts around this

      CURRENT_VERSION=$(antidote -v | awk '{ print $3 }')

      OUTPUT=$(curl -s https://api.github.com/repos/mattmc3/antidote/releases/latest)
      LATEST_VERSION=$(echo $OUTPUT | grep tag_name | awk '{ print $2 }' | cut -d '"' -f 2 | awk '{ print substr($0, 2) }')

      if [[ "$CURRENT_VERSION" != "$LATEST_VERSION" ]]; then
          echo "Current version: $CURRENT_VERSION, Latest version: $LATEST_VERSION"

          ZIPBALL_URL=$(echo $OUTPUT | grep zipball_url | awk '{ print $2 }' | cut -d '"' -f 2)
          TARBALL_URL=$(echo $OUTPUT | grep tarball_url | awk '{ print $2 }' | cut -d '"' -f 2)
          
          ANTIDOTE_LOCATION="${0:A:h:h}"
      fi

Maybe ask the user if you want to replace the files at ANTIDOTE_LOCATION.

• Download the zip/tar to /tmp
• Delete ANTIDOTE_LOCATION
• Extract zip/tar at ANTIDOTE_LOCATION

[mattmc3]

Genuinely curious - what's the rationale for supporting updates this way? The zip releases are there for package managers. If you want self update to work the recommended installation via git clone already handles this. I'm not seeing a benefit to supporting self update for manual installation.

[mavwolverine]

Won't the git clone way be the bleeding edge. git pull will get the latest changes from master branch.

The releases approach allows me to use stable release.