3 ms·
> Snap was here before flatpack, what should a company like Canonical do if they want to try something new? Use planted developers in GNOME or other projects to
by tapoxi 8y ago
> Snap was here before flatpack, what should a company like Canonical do if they want to try something new? Use planted developers in GNOME or other projects to push projects as dependencies into all distributions?
They shouldn't hardcode Snap to depend on snapcraft.io, its really that simple.
- simion314 8y agoI understand that, maybe they will do it in future or someone will fork it to change the store url,,, but do we want each distro to create it's own snaps, we get back to duplicated efforts in packaging and review(snap team reviews apps that ask for elevated permissions)
- HeadsUpHigh 8y agoNot every distro but different stores with different policies for including snaps. I personally am completely uninterested in using any of the security and usability disasters that are the new universal package types but that would definitely make sense.
- simion314 8y agoSnaps could work great on servers, at work we have a CentOS server (via hosting is not our own), I am a developer not a sysadmin and I don't want to mess with the package manager and break something on this server(it is running a bunch of stuff)...anyway today I had to download and run a linux binary , it was a .tar.xz and it worked, would have been even better if I could be sure this binary was sandboxed. On the desktop I use Kubuntu LTS, snaps will allow me to test or run software that is not in the repo or it is an older but sable version in the repo, IMO snaps provides extra options so if you do not need it you should not use it.