162
submitted 1 year ago* (last edited 1 year ago) by cyclohexane@lemmy.ml to c/linux@lemmy.ml

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.

you are viewing a single comment's thread
view the rest of the comments
[-] jsveiga@sh.itjust.works -1 points 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?

[-] cyclohexane@lemmy.ml 1 points 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 0 points 1 year ago* (last edited 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.

[-] cyclohexane@lemmy.ml -1 points 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 1 points 1 year ago* (last edited 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?"

this post was submitted on 01 Aug 2023
162 points (95.0% liked)

Linux

48334 readers
647 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS