-
Notifications
You must be signed in to change notification settings - Fork 14
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
Dev channel support #14
Comments
We could probably have a totally different snap, named sublime-text-dev to follow the dev releases instead. |
Hmm yeah that could be one workaround but perhaps not the ideal solution? It seems that the snap channels are designed to let us use one package name with multiple version options (stable vs. beta/dev etc). I might give this a go soon (unless someone beats me to it haha) 😁 |
Just put up a quick PR with my thoughts #15 😄 |
More than a different snap, I'd prefer to add a different version track for this, so that users can just follow dev track |
Yeah @3v1n0 that's my hope too, bit more of a recent discussion over on this Pull Request #15 |
We could probably get this going in a similar way to the |
This is now done! You should be able to |
Hey @om26er, love your work!
I just want to clarify if using the dev channel (https://www.sublimetext.com/3dev) is possible via this snap? I've seen your discussion with Will Bond on the official forums, but maybe the dev channel idea hasn't been implemented yet?
It looks like the --edge snap channel installs the latest stable version (3170, previously 3143) at the moment:
As a licensed user, I would love to be able to use this snap for Sublime Text's dev channel (e.g. 3168, 3169, 3171 once it's out) so I can stay up to date with the bleeding-edge.
Cheers,
Kyle
The text was updated successfully, but these errors were encountered: