• 520@kbin.social
      link
      fedilink
      arrow-up
      6
      ·
      edit-2
      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
        link
        fedilink
        arrow-up
        2
        ·
        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
        link
        fedilink
        arrow-up
        1
        ·
        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.