We need to track these a bit differently, as we can never actually update a tarball-based install. The easiest solution is to assume the url will change, and if the url has changed, force-reinstall.
We can track this inside of a .archive-url file that is created within the plugin. If that file exists, we use that to compare whether we should force install the plugin against.
Conversely, if it exists, trying to update the plugin should write an error to stderr so users know that the plugin must be "reinstalled" in order to be updated. That, or update should take a tar url that is only useable for archive-installed plugins (and errors if we try to install over a git-installed plugin).
We need to track these a bit differently, as we can never actually update a tarball-based install. The easiest solution is to assume the url will change, and if the url has changed, force-reinstall.
We can track this inside of a
.archive-url
file that is created within the plugin. If that file exists, we use that to compare whether we should force install the plugin against.Conversely, if it exists, trying to update the plugin should write an error to
stderr
so users know that the plugin must be "reinstalled" in order to be updated. That, orupdate
should take a tar url that is only useable for archive-installed plugins (and errors if we try to install over a git-installed plugin).