832
you are viewing a single comment's thread
view the rest of the comments
[-] 520@kbin.social 17 points 1 year ago

The main reason is that it is completely controlled by Canonical, with no way to add alternative repos.

[-] JoeyJoeJoeJr@lemmy.ml 2 points 1 year ago

It's worth noting you can bypass the repo, and install snaps that you downloaded from some other source - see https://askubuntu.com/questions/1266894/how-can-i-install-a-snap-package-from-a-local-file.

That doesn't give you a separate "repo," but it does allow you to install snaps from anywhere.

[-] 520@kbin.social 6 points 1 year ago* (last edited 1 year ago)

You can, but that completely negates the reasons why you'd want to have a repo system in the first place. You gotta do the legwork to get updates, for example.

[-] jj4211@lemmy.world 2 points 1 year ago

And to be explicit about it, zypper, dnf, apt, flatpak all have a specific mechanism to declare repositories and one 'update' check will walk them all.

snap does not, and manually doing a one off is useless. AppImage also has no 'update' concept, but it's a more limited use case in general, it's a worse habit than any repository based approach.

[-] JoeyJoeJoeJr@lemmy.ml 1 points 1 year ago

This isn't necessarily true - a developer choosing to not include their app in a repo can always opt for a self-updating mechanism.

Don't get me wrong - repos and tooling to manage all of your apps at once are preferred. But if a developer or user wants to avoid the Canonical controlled repo, I'm just pointing out there are technically ways to do that.

If you'd question why someone would use snap at all at that point... that would be a good question. The point is just that they can, if they want to.

this post was submitted on 02 Oct 2023
832 points (95.7% liked)

linuxmemes

21281 readers
606 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS