Linux

125 readers

1 users here now

founded 2 years ago

How do you think about Snap? (kbin.social)

submitted 1 year ago by wave_walnut@kbin.social to c/linux@kbin.social

26 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] this_is_router@feddit.de 5 points 1 year ago* (last edited 1 year ago) (2 children)

IMHO: It's bullshit, wastes resources, ubuntus server implementation is proprietary and it fragments the package management of a distro. Snap is the worst, flatpak and appimage are tolerable since they are at least open source but i personally try to avoid these "solutions" like the plague.

apt for the win...

[–] phi1997@kbin.social 6 points 1 year ago

Eh, when Debian doesn't have the latest version of dependencies, Flatpak is necessary. Flatpak will long-term likely be great for running abandoned legacy software too.

[–] christophski@feddit.uk 3 points 1 year ago (1 children)

People always complain about "dependency hell" with apt, but I've always found it to be the perfect solution

[–] this_is_router@feddit.de 1 points 1 year ago* (last edited 1 year ago)

Me too, you just need to avoid installing packages from repos that are not for your distribution. And live with the package versions until the next release is ready