Building native packages is complicated
xeiaso.net
Especially if you want a UX as good as Docker images give you.

Anubis provides protection against bots scraping websites and DDoSing projects.

This blog post is about Xe’s reasoning for originally only providing docker packages and their work to provide native packages.

  • onlinepersona@programming.dev
    14·
    2 days ago

    There must be a tool that allows you to build packages for multiple systems in multiple formats (deb, rpm, nix, flatpak, snap, etc.). Does that not exist? After 20 years of these systems existing, somebody must’ve tried…

    Also, it’s clear that once again, open source needs some kind of funding model, because it’s a little crazy that a project like this can get so popular so fast, the dev flooded with praise, thanks, and issues but not money to maintain and develop it.

    Anti Commercial-AI license

      • corsicanguppy@lemmy.caEnglish
        1·
        1 day ago

        makefile which packages as tarball, deb, rpm and appimage.

        Packaging an RPM in a makefile? That’s inside-out.

    • Shayeta@feddit.orgEnglish
      9·
      2 days ago

      Problem is that distro1 has req-lib2.5.3 while distro2 has req-lib2.7.8, but your project was developed on distro3 with req-lib2.9.5 so you have to deal with every distro having different lib versions and compatibility issues that come with it, not just different packaging formats.

      • MrSoup@lemmy.zip
        4·
        2 days ago

        And different names too. Debian and Fedora have different packages names, so req-lib on debian becomes req-devel on Fedora.

    • corsicanguppy@lemmy.caEnglish
      12·
      19 hours ago

      a tool that allows you to build packages for multiple systems in multiple formats (deb, rpm, nix, flatpak, snap, etc.).

      Given flatpaks and snaps are toxic, the other ones - deb, rpm, pkg - can be packaged relatively easily. It’s all a separate effort with files and meta-info that doesn’t often intersect, but it’s manageable. It lends itself incredibly well to the trivial ‘automation’ that gitlab, forgejo and other major git suites provide.

      Source: did this for the entirety I built and maintained a software suite for linux and unix, for like 15 years. I built some code, I packaged it. Because anything less isn’t really ISO27002.

      TL;DR - the ‘tool’ is a simple script and your brain. the biggest hurdle is the unknown itself and, once you get to it, the work can be pretty straightforward.