Linux

48386 readers

985 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]

140

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]

69 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)

When debian maintainers need to release an update of a debian package, they need to make sure it doesn't break compatibility with ... other debian packages - yes maintained by other people. They don't need to test it with a dozen *ubuntu and other .deb variants, nor coordinate with those other maintainers and wait for them to release their new, compatible versions.

It's already hard to do that within the same distro.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

I am not sure if you are onto something or you don't understand the proposition. e.g. how does KDE or any other DE developer maintain their packages on debian? Do they not? And its up to debian developers to decide what version of KDE they use? If thats the case then I see your point, which would make it very hard for the so-called "kubuntu" package maintainer, because they have to rely on what debian maintainers do.

uses their

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago)

Yes, that's what I mean. For example suppose you had this mixed solution (core comes from debian repository, "kubuntu personality" from kubuntu repository).

Then debian maintainers release updates for their packages - which they tested and validated in systems that use only other debian packages.

Next time you update your system, it may happen that the new version of debian components are no longer compatible with the kubuntu components.

Debian won't wait for or check if every distro who uses their "core" has tested debian changes and released compatible new packages of their own.

Probably most debian based distros simply repackage many base debian components with minimum or no changes, but they know those releases are compatible with their own "customized" packages, and can have control of their dependencies.

Edit: I didn't address one of your questions directly: No, developers and maintainers of a linux system component (as kde, and even the kernel) not necessarily are the maintainers of a specific distro packages.

For example, kernel decelopers and maintainers release a new kernel release independent of any distro. It's up to the distro maintainers to test and package this, then make it available in their repo.