Author

Topic: Feature Proposal - Armory Snap Package (Read 513 times)

newbie
Activity: 7
Merit: 0
September 23, 2016, 10:04:23 PM
#5
I personally don't think it is necessary. However, if there are a lot of users on other linux distros that would like a packaare .onion sites securege, then we can make such packages.

We'll see what the feedback is like. I've been interested in a fedora package for a while.

Support all possible use cases > Support only debian derivatives 

There is a debian package. You have to download it from where we upload binaries on github.

Sorry, I was referring to the debian repository. The installation process is manual. Snaps allow for a debian-like installation experience but go around the debain packaging politics.
staff
Activity: 3458
Merit: 6793
Just writing some code
September 23, 2016, 09:42:51 PM
#4
My belief that a snap package would be beneficial is what prompted the proposal. However, what I believe isn't important. I've never built a snap package and don't want to unless you guys reasonably believe that doing so would be beneficial. Does the development team and the general userbase believe that migrating to the new package format would be beneficial?
I personally don't think it is necessary. However, if there are a lot of users on other linux distros that would like a package, then we can make such packages.

From memory, my understanding is that no debian armory package exists because because of debian's politics with respect to updating Armory. Instead of just having a debian package and circumventing debian's packaging politics, we can also have a package that works on all major distros.
There is a debian package. You have to download it from where we upload binaries on github.
newbie
Activity: 7
Merit: 0
September 23, 2016, 09:39:01 PM
#3
If you think that it is useful, you can make one and submit a pull request and we will consider it.

My belief that a snap package would be beneficial is what prompted the proposal. However, what I believe isn't important. I've never built a snap package and don't want to unless you guys reasonably believe that doing so would be beneficial. Does the development team and the general userbase believe that migrating to the new package format would be beneficial?

From memory, my understanding is that no debian armory package exists because because of debian's politics with respect to updating Armory. Instead of just having a debian package and circumventing debian's packaging politics, we can also have a package that works on all major distros.

Firefox, VLC, Docker, and others are migrating to this package format.

http://www.pcworld.com/article/2942267/why-ubuntu-plans-to-replace-traditional-linux-packages-with-something-better.html
http://www.pcworld.com/article/3060143/linux/mozilla-will-provide-firefox-as-a-snap-package-for-ubuntu-cutting-out-the-middleman.html

I'm not trying to sell this but it makes sense to me. Snaps appear to be the future of application packaging.
staff
Activity: 3458
Merit: 6793
Just writing some code
September 23, 2016, 08:56:27 PM
#2
If you think that it is useful, you can make one and submit a pull request and we will consider it.
newbie
Activity: 7
Merit: 0
September 23, 2016, 08:54:56 PM
#1
It would be beneficial for armory to be packaged using the new snap package format because doing so will allow armory to run on all major linux distros, all of the software needed to make armory work can be bundled into the snap, a common linux end user experience can be realized, the armory installation will be sandboxed, and the installation process will be greatly simplified and standardized.

Is there any interest in an armory snap package? Has anyone built an armory snap?

http://snapcraft.io/
http://snapcraft.io/create/
Jump to: