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.

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

    You’re making a lot of assumptions about me that could be easily answered if you read my original post. No I do not think that that’s the only difference between any two distros. My post is specifically talking about distros that only change non-system software (and most of them only change GUI).

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

      And could you identify (and get all such distros and their “core distro” source to agree on) what exactly are the “system software”, which the “customizers” must never ever need to change, and that the “core distro” will forever have to coordinate with their “partners” before any new release or update?

      Can’t you see it would be a lot of extra work and risk for maintainers, just to make your distro hopping (maybe) quicker?

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

        what exactly are the “system software”, which the “customizers” must never ever need to change,

        To clarify, I am not saying that maintainers should not modify software. I am saying that if they don’t, that making a whole different distribution is overkill and over complicated, and it is much easier for both them and the user to have it as a package instead.

        For releases, it would be simply done just like any other package. There’s a vast number of packages that already do everything you can imagine, and they have none of the show stopping troubles you speak of.

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

          Well, they do, and even when they don’t, they won’t commit not to forever, just to help distro hoppers.

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

            Well, they do

            Again, the ones who do, not talking about them

            they won’t commit not to forever

            Sounds like Over-engineering syndrome. Should every packager just write their own OS just in case they find that they need to? Maybe every application developer should just write an entire kernel just in case too. Take that distro hoppers!