[bisq-network/bisq] Initial commit of Snap package (#2378)

[Devin Bileck]

To be honest, I am unfamiliar with snap packages and this is my first time looking into it. The more I look into it, the less inclined I am to suggest the snapcraft store as a way to distribute Bisq (or any Bitcoin application for that matter) as I have not found a way to verify the application against our signature files (and ideally it should be verified before installing via snap in the first place). @HarryMacfinned highlighted these same concerns in https://github.com/bisq-network/bisq/issues/568.

Up until this point, we have only provided DEB packages with our releases which is serving only a subset of the Linux community, and with our next release we will be able to provide an RPM package (see https://github.com/bisq-network/bisq/pull/2200), which will help cover a wider audience.

We could potentially provide a snap file with our releases (along with signature file) as it can be installed locally. For example (as per https://docs.snapcraft.io/java-applications/7819):
> sudo snap install bisq-desktop.snap --devmode --dangerous

But this kind of defeats the purpose of using snaps as an easy install/update app-store.

However, since snaps can be used on all major Linux distributions (according to https://docs.snapcraft.io/installing-snapd/6735), providing a snap package would allow us to provide an install package for the majority of the Linux community.

But to be honest, this may not warrant the added effort as it is likely the rest of the Linux community is skilled enough to just build the application from source.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/pull/2378#issuecomment-461324463
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190207/b4fcd213/attachment.html>