-
Notifications
You must be signed in to change notification settings - Fork 31
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
Provide some sort of update mechanism #6
Comments
AppImage's have update possibility, but I did not implemented (yet.. and not sure if i'll come to that). PPA would be nice, but the debian packaging is still a bit mystery to me, so I'm currently waiting, whenewer Art will be so kind to help with PPA (he did for upstream repository). |
It beginning I did not even plan to provide binaries... I just wanted to make few improvements and post few PRs to upstream... So I'm already quite ahead of the plan anyway :) |
So here is the new PPA for Ubuntu: https://launchpad.net/~robert7/+archive/ubuntu/nixnote21 |
Wow thanks! Does installing from this PPA imply that it'll gracefully upgrade an existing 2.0.2 install from nixnote2-daily PPA? And I'm assuming its also safe to remove the nixnote2-daily PPA - yes? |
The new PPA is independent from both official "nixnote2" package and the "daily nixnote2 PPA". This is because the original maintainer @baumgarr isn't available. That means the v2.0 will not automatically upgrade to v2.1 - you need to take action to subscribe to the new one. I felt some people were not yet fully confident with making "clear cut" upgrade, so I renamed both the application and the package to "nixnote21". That means you can have both installed: To install "nixnote21" enter |
That's good information, thanks. Everything worked like a charm! Should this PPA be considered to be a daily / weekly / whenever style of releases? Or whenever there's a version number bump? Or something else all together? |
The idea is, that the "nixnote21" PPA should be the "stable build". In the future it should build automatically, whenever there is push into master branch - and this should happen, when there is version number change. |
exactly, robert, you can create a daily PPA which automatically builds on every commit, so that people who want the very latest features take their own risk. Then you decide based on your testing when to release that as a stable build in the main PPA |
@artmg : yes |
Configuration of the PPA should be now finished.
As some users already installed the binaries from the two now obsolete PPAs, I pushed special app version in the old PPAs which will display info about the required repository change and point users to a wiki page with explanation and few commands, which will do the fix: https://github.com/robert7/nixnote2/wiki/NixNote-PPA#ppa-url-change-201809 The binary name and the package name is now This also means, only one version of the native |
Can confirm that everything works as you've published in the wiki. Also liking the updates. Thanks again for all your work! |
Thanks for keeping Nixnote going (an thank for referring me!)!
Not sure if its possible with appimages but a PPA for Ubuntu or some sort of automatic updating mechanism is desirable. I know snaps can update themselves - not sure of what's possible with appimages. Is there already an easy way that I'm missing? Or is there an easy way to set something like this up?
The text was updated successfully, but these errors were encountered: