Snap created and ready for publication #1003
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Prior to upstream PR.
|
Hi @tsl0922 - reaching out again regarding the forum thread I posted above. I'm attempting to publish this snap as a "classic" snap - meaning I need your approval to do so. If you are willing to allow that, do you mind responding here or providing a response in the forum thread? |
|
I can help publishing it to snap store, but it seems the name |
|
Yes I registered it - created the snap and I'm ready to publish it. Just need your permission. If you'd rather manage it all, you'll need to join the forum thread and open discussions with the snapcraft team. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
I've recently created a snap for ttyd and have it working with classic confinement. Meaning it will run "as native" within a snap container for any Linux distro supporting
snapd. Learn more about snaps here.I am happy to maintain the snap for your project, unless you'd prefer maintaining it all "in-house". There's not much anyone on the team would have to do, as the snaps are automatically built and published on the snap store.
As part of the security checks, pedigree, and validation, the upstream team/devs should at least know about it and agree with the publication as a
classicsnap. Basically, the snap will much like a.debor.rpmon another distro supporting those packages; except it's distro agnostic.I hope this comes as a welcome PR. If you'd like to be involved in the convo with the snapcraft team, please see this thread.