Skip to content
New issue

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

Add a Way to Automatically Upgrade #12

Closed
Shinmera opened this issue Aug 6, 2016 · 3 comments
Closed

Add a Way to Automatically Upgrade #12

Shinmera opened this issue Aug 6, 2016 · 3 comments
Labels
elisp Problems related to the elisp code shipped with Portacle features

Comments

@Shinmera
Copy link
Member

Shinmera commented Aug 6, 2016

There's a command to automatically pull new sources, but that doesn't update the binary parts. It should be possible to easily move on to the next release without losing all your projects and configurations or having to do it manually yourself.

@Shinmera Shinmera added features elisp Problems related to the elisp code shipped with Portacle labels Aug 6, 2016
@Shinmera
Copy link
Member Author

Shinmera commented Sep 24, 2016

I think the easiest way to do this would be to add a "VERSION" file that stores the latest major version. This can then be used to automatically construct the path to the download archive on Github without having to scrape any HTML files for the info.

As mentioned on the other ticket, doing this automatically would also require Windows to switch to a zip for the deployment as we cannot extract an exe automatically. I'm also not sure how things would work with upgrading the file while it's being executed. I think particularly on Windows that will be an issue.

@Shinmera
Copy link
Member Author

Shinmera commented Oct 7, 2016

Actually, GitHub features a releases/latest link that could be used, but has to be HTML-scraped to get the version out of. Should be a better idea than the VERSION file though since that file will otherwise get pulled in by a regular update that fetches the git versioned sources.

@Shinmera
Copy link
Member Author

Shinmera commented Oct 9, 2016

I'm not sure if this is worth the effort and potential for broken behaviour. Given what I've been able to tell so far there's multiple issues:

  • Windows does not have a native tar.xz extractor and as such we need to have the initial ship in EXE format. The SFX I can produce don't allow specifying where to extract, so it cannot be fully automated. We could also ship a windows version as a ZIP or such-like, but the effort is probably not worth it.
  • Getting the latest version requires scraping HTML which might break at any time.
  • Replacing the sources while portacle is still running can and will cause problems. Tricks would have to be pulled to avoid that.

After all this I don't think it's a good idea to keep this for a 1.0 release. I might reopen this if I feel courageous, or if someone else has ideas on how to fix all of the above.

@Shinmera Shinmera closed this as completed Oct 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
elisp Problems related to the elisp code shipped with Portacle features
Projects
None yet
Development

No branches or pull requests

1 participant