this post was submitted on 17 Jun 2023
0 points (NaN% liked)

Linux

5 readers
1 users here now

founded 2 years ago
 

I'm very beginner of Linux server admin. Few days ago I set up snap version of nextcloud server app on my own Ubuntu VPS server, and I found that Snap system might be focused to build original file system hierarchy in /snap directory, and I felt a little weird about that.

For example, Linux file system hierarchy is defined to set server app config into /etc/app/conf.d or so.
But snap version app tend to set it into /snap/app/current/app/config or so.
It sounds so complicated for me.

So I want to know about how Snap is thought by others. I'm happy if you might tell me something here.

top 8 comments
sorted by: hot top controversial new old
[–] Gourd@kbin.social 0 points 1 year ago

It's annoying fragmentation when even for a stable distributable package there's flatpak as a standard, and I've never seen why Ubuntu needs their own with a proprietary store.

Like I generally tend to favor native packages, but I can at least appreciate Flatpaks having advantages and times even I want to use them. (Largely when stuff is a pain to compile on Arch for library reasons.) Snap is a non-universal universal package format.

(Also going to shout out AppImages, which are an entire package as a single ELF file you can run on basically any distro. I'm not sure how good they are for important work, but I just think they're neat and have come in handy for running stuff on old CentOS in the past.)

[–] Bero@kbin.social 0 points 1 year ago

For server software I prefer docker/podman,
For desktop apps I prefer native and then flatpaks

[–] tuxiy@kbin.social 0 points 1 year ago (1 children)

Why bother when you have flatpak?

[–] linuxfiend@kbin.social 0 points 1 year ago

Because you're Canonical?

[–] Jarmer@kbin.social 0 points 1 year ago

I simply don’t understand why snaps exist in 2023 with the existence of flatpaks.

[–] stdevel@kbin.social 0 points 1 year ago

The problem I have with Snap is that it's a rather mediocre over-engineered technology (e.g. decompressing images had poor performance for a long time; see the Firefox snap drama) that is pushed very hard by Canonical. It has a closed-source market and nobody knows what Canonical does on their side for performing anti-malware scans (that haven't been very reliable in the past). That's not how open-source works. We want to have a decentral approach like Flatpak repositories have.
Flatpak is my default, but sometimes I also use AppImages.

[–] Meshuggah333@kbin.social 0 points 1 year ago

They're slow, I vastly prefer Flatpaks.

[–] asteroidrainfall@kbin.social 0 points 1 year ago

I only use it for my #Nextcloud instance. #Snap does make it easy to upgrade or rollback and configure. That said I wouldn’t use it for anything else and would probably use the #docker image next time.