Linux

48400 readers

708 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

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

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

founded 5 years ago

MODERATORS

[email protected]

163

Opinion: Distributions that only change non-system pre-installed software or desktop environment should instead be packages or scripts (lemmy.ml)

submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]

80 comments fedilink hide all child comments

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

[–] [email protected] 1 points 1 year ago (1 children)

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?

[–] [email protected] 1 points 1 year ago (1 children)

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.

[–] [email protected] 1 points 1 year ago (1 children)

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

[–] [email protected] 1 points 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!