The majority of Linux distributions out there seem to be over-engineering their method of distribution. They are not giving us a new distribution of Linux. They are giving us an existing distribution of Linux, but with a different distribution of non-system software (like a different desktop environment or configuration of it)

In many cases, turning an installation of the base distribution used to the one they’re shipping is a matter of installing certain packages and setting some configurations. Why should the user be required to reinstall their whole OS for this?

It would be way more practical if those distributions are available as packages, preferably managed by the package manager itself. This is much easier for both the user and the developer.

Some developers may find it less satisfying to do this, and I don’t mean to force my opinion on anyone, but only suggesting that there’s an easier way to do this. Distributions should be changing things that aren’t easily doable without a system reinstall.

  • jsveiga@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    arrow-down
    2
    ·
    1 year ago

    I do not suggest they should!

    No? do suggest debian kept their install package frozen forever just to make this proposition viable?

    • CyclohexaneOPM
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Would would they do that? You act as if debian doesn’t already package a massive amount of software, and has no issue adding on to the list.

      • jsveiga@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        edit-2
        1 year ago

        They test that massive amount of packages to make sure the dependecies and compatibility are kept. They do that between DEBIAN packages. The maintainers of the bash debian package can’t just shove a new release in the repository. It’s tested in DEBIAN systems first.

        Who would test this new bash package in every fskcing “addon distro” that installs on top of “core debian” before releasing it to the debian repository? Or would the maintainers of every fscking distro have to scramble to update their packages after debian released this, and users have updated, breaking compatibility with the “addon” packages?

        Or the opposite, the “addon” distro package developers want to use a new feature from a library, but can’t, because debian hasn’t updated their packaged version yet.

        • CyclohexaneOPM
          link
          fedilink
          arrow-up
          1
          arrow-down
          2
          ·
          1 year ago

          youre over complicating it. Debian adds new packages to its repository all the time, and this would be just one more package they add. Simple as that.

          • jsveiga@sh.itjust.works
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            1 year ago

            ha, so you don’t mean having multiple distros dropping their “base systems” and only providing the “addon” part in their repos, but actually having the “core” distro include all the “addon” flavors into their repo. haha really, really “simple”.

            “Hey debian, I’m a one man operation out from North Korea, and I made this customization package. I swear it complies with every privacy and security policies, and that it is compatible with your core system. No it won’t break anything. Can you please include it in your repo?”