On Debian-based distros, when an app is available as a DEB or an AppImage (that doesn’t self-update), but no APT repository, PPA or Flatpak, the only option is to manually download each update, and usually manually check even whether there are updates.

But, what if those would be upgraded at the same time as everything else using the tools you’re familiar with ?

dynapt is a local web server that fetches those DEBs (and AppImages to be wrapped into DEBs) wherever those are, then serves these to APT like any package repository does.

I started building it a few months ago, and after using it to upgrade apps on my computers and servers for some time, I pre-released it for the first time last week.

The stable version will come with a CLI wizard to avoid this manual configuration.

Feedback is welcome :)

  • markstos@lemmy.world
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    11 days ago

    No matter where you install from, you have to trust the source. Indeed, you have to trust every step in the supply chain.

    If you are getting your code straight from the author, you are eliminating an exploit that’s introduced by a compromised account of a packager.

    Carry on.

    • cqst@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      1
      arrow-down
      3
      ·
      11 days ago

      If you are getting your code straight from the author,

      Which is not what you are doing at all with a .deb file. A .deb file is a binary with a bunch of scripts to “properly” install your package. Building from source is what you SHOULD be doing. Debian has an entire policy handbook on how packages are supposed to be packaged. Progrmatically you can review the quality of a package with ‘lintian’. .debs made by developers following a wiki tutorial can’t even come close. remember, apt installs happen as root and can execute arbitrary code.

      Also, debian packagers can be project maintainers, so they can be “the author.”