Working snap created #117
Merged
Working snap created #117
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
- Snapcraft yaml - GH Workflow - test-snap-can-build - Updated README with snap instructions
noahgorstein
requested changes
Aug 31, 2024
There was a problem hiding this comment.
Hey @kz6fittycent - thanks for your contribution!
I'm happy to let you maintain the snap for jqp.
if you don't mind just cleaning up the typo in the readme, I'll merge it after that.
|
Thanks @noahgorstein I need to add that workflow to my own repos! I can't tell you how many times I've missed typos. |
Added more info
|
The snap has been published! Thanks for working w/ me on this. |
noahgorstein
approved these changes
Sep 12, 2024
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
jqpand have it working with strict confinement. Meaning it will run "as native" within a snap container for any Linux distro supportingsnapd. 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 of the snap. 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.
New files: