Any plans on making a snappy packages? (Question) about lazydocker HOT 6 CLOSED

I'm happy to do this if I can get some guidance on what needs to be done :P

from lazydocker.

I'll try to tackle this today.

from lazydocker.

I made two variants:

• added snapcraft.yaml
• modified .goreleaser.yml

master...dawidd6:snapcraft

IMO goreleaser would be better in that case. Already tested it, builds and runs fine.

from lazydocker.

If there is such demand, I could do it by directly contributing snapcraft.yaml to this repo.

But I would better like not to be the one who uploads to Snap store.
Definitely would be the best if the uploader was the original creator of software. @jesseduffield

NOTE for Jesse: you already have a launchpad account so there is simply no need to make another account and Canonical provides this service for automatic builds straight from Github repo.

from lazydocker.

If there is such demand, I could do it by directly contributing snapcraft.yaml to this repo.

But I would better like not to be the one who uploads to Snap store.
Definitely would be the best if the uploader was the original creator of software. @jesseduffield

NOTE for Jesse: you already have a launchpad account so there is simply no need to make another account and Canonical provides this service for automatic builds straight from Github repo.

Agreed.

Personally, I would prefer to have the snappy package available for download instead of having to manually download the linux binary myself, but that's just me being lazy!

from lazydocker.

Seems like you are using goreleaser and it has snapcraft support:
https://goreleaser.com/customization/#Snapcraft

Maybe we should do it this way?

Also, I think that classic confinement will be required, because using strict one, lazydocker cannot communicate with docker installed not as snap. Which leads us to another problem - classicaly confined snaps need manual approval from Canonical, to be accepted into Store. It's a single action, but still.

from lazydocker.