-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
Official snap for Snapstore #7016
Comments
@casabre thanks for this and the offer! I've submitted a request to get hold of the |
@yossigo you are welcome and I would be happy to contribute. Regarding a dedicated repository, I would stick with it because if you link the repository with the snapstore, one can utilize the provided CI which is building and publishing the snap. Sounds more reasonable to me but it’s up to you 😉. |
So it seems I'm a bit late to the party 😅
While creating a separate repository has a lot of benefits such as being a place for snapcraft specific discussions, issues, and docs, it has however a pretty significant downside as I'll point out below. There are a few questions left though, I'm gonna list them here in no specific order:
Further changes I implemented in my fork:
The big question remains, should we put the snap config in a separate repo and pretty much give up on building edge and candidate releases? I'd vote for integrating it into the main project as publishing a new edge release on every github commit, a candidate on -rc tags, and a stable on normal tags seems the most optimal for me. This could be archived with a bit of shell magic and the I know this is a lot, but I just want to help ( and also use the redis snap 😃 )
|
@casabre @JonasKruckenberg After some consideration and discussion with other Redis core team members, I've adopted the separate repository approach. As we'll push for more native packaging, it makes sense to keep the core repository clean. We'll be sure to integrate Snap releases in any official/RC version released anyway, and I think running a daily job of building the latest unstable is probably frequent enough. I've done some basic work to automate building and publishing of an unstable version as an edge. I'll appreciate if you can have a look and suggest any improvements/fixes you see fit! I have absolutely no familiarity with the snap ecosystem so I may have done lots of dumb things, don't spare me please. Any further discussions/PR can probably go to the new repo. |
@JonasKruckenberg thanks for your thoughts on this and sorry for the late reply. @yossigo thanks for setting up a new repository.
I am not sure how can we manage this fully automated. Maybe some connected actions which are updating the version in the snap repo because I believe that not that much modifications are necessary in the recipe. However I am not sure if an automated trigger of builds.snapcraft.io is possible? Do you have more experience on this side?
Just left the original commands because I wanted the alias replacement after publishing by the snap store
This is great. I just used it as initial playground
Usually I would agree but do we have much more benefits from switching compared to the core LTS 16.04? With LTS 16.04 core compatibility, I believe we can reach much more users
Honestly, I can not remember but I believe that it was a build dependency for the snap core. @yossigo I had just a quick glance but from my side LGTM. |
@casabre Thanks, I will wait for more feedback before putting together a more stable 6.0.6. |
I actually don’t know, the last time I tried I couldnt get it to work on anything other than push, but I'll do some more testing tomorrow.
I think the core snap doesn't really matter when it comes to compatibility, for example I can install the redis base20 snap on my ubuntu 16 VM without problems. But maybe there are more subtle differences that I don't know of |
The unstable snap got no rejects, so there's now a stable Thanks @JonasKruckenberg and @casabre for your help! |
I would love to be able to deploy redis as a snap in my setup. Thus, I created a recipe in order to build the snap successfully. Unfortunately, I cannot release it at the Snapstore because the package name "redis" is reserved for official packages by the developer.
Hence, I would ask if it is possible to transfer the ownership of my repository to antirez and that you are applying for the official package name. In the end, I could offer to maintain the package and the recipe.
Does this sounds reasonable to you? Thanks
The text was updated successfully, but these errors were encountered: