this post was submitted on 01 Aug 2023
2 points (66.7% liked)
Linux
48329 readers
639 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Suppose kubuntu, ubuntu, lubuntu, xubuntu were packages to be installed on top of debian.
How would you do that? Debian would not create and maintain a "core debian" variant just to be installed then receive the extra packages. Would the *ubuntu packages replace, instead of add on top of default debian packages?
Then where would the updates come from? Both debian and *ubuntu repositories?
What about dependencies? Would debian have to coordinate with all *ubuntu maintainers (and they too, between them) for compatibility tests every time debian needed to update one of its packages? Or they'd just update and *ubuntu would have to scramble to release fixes for what had been broken?
Not to mention convenience; would you have to download debian, download *ubuntu, install debian, then your *ubuntu?
Why not then package the "core debian", with the tested component versions that work with the *ubuntu packages you're downloading? Hey, and what about script the installation to install both "core debian" parts and then *ubuntu automatically? That's an innovative idea indeed. No, wait, isn't it sort of what they already do today?
It's not like there's a Linux headquarters with a centralized organization that releases all multiple distros just to feed the hobby of distro hoppers. Distros are maintained and packaged by different people, and it's already a lot of trouble to keep each part in sync.
To be honest, I do not fully understand your question here. Could you rephrase?
They must not replace. If they are merely installing KDE on top of Ubuntu, then theres nothing to do here. The work is already done for us. But if it is doing more than taht, then they should be different packages building on top of the default debian packages for KDE et al.
Sort of like how LunarVim is a distribution of NeoVim. It is the same NeoVim, but with pre-configurations and plugins shipped OOTB, and it can be packaged separately.
Thats the beauty of this. Package managers are already equipped with dependency management. It is far easier to manage dependencies with a package rather than rolling out your own distribution. It is literally one of the biggest reasons why we use package managers to begin with. We dont want dependency hell!
This is a debian specific question, so I will try to answer more generally. It would just have to be done in the same way any package is maintained on that distribution. And this varies by distro; some distributions have different workflows for their package maintenance. The point is that we make use of these already defined workflows that have worked for decades and been iterated on. It is much easier to package than to create a new distribution.
Instead of installing *ubuntu, you install Debian, then run one command:
sudo apt install *ubuntu. I see these as nearly equivalent. Moreover, it could be made to be an option in the distribution's installer, sort of like EndeavourOS and Fedora do it.That can be what I mean with it being an option in the installer. But if you mean maintaining a whole separate distribution just for this, well ... you are maintaining an entirel separate distribution just for this ... instead of just maintaining a package.
You fail to realize that each distro is maintained by different people. Your reasoning would make sense if the "core debian" was maintained and packaged by the same people who maintained and packaged *ubuntu.
The end user would download "core debian" from debian, and the *ubuntu "flavor" from *ubuntu. Installing debian then going "apt install kubuntu" wouldn't work because kubuntu is not in the debian repository.
If debian changed their downloadable "core debian", it could make it incompatible with what's in the kubuntu repository. They are not maintained by the same employees of "Linux inc."
I very well realize this. Packages are maintained by different people too!
The idea is that installing a *ubuntu would literally be the same as installing one of the many packages already available. It works for all those packages, so why wouldn't it work here?
Yes, that is correct. I apologize if you misunderstood what I said. I did not mean to say that this is the current state. This is what I think how things should be.
Though for the case of kubuntu, it apparently is pretty close. You can in fact already do "apt install kubuntu-desktop", but you have to be on regular Ubuntu instead of debian. Which is fine, since Ubuntu changes a lot more about debian than just pre installed packages, so it works out for my example.
I do not suggest they should!
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.
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.
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.
No? do suggest debian kept their install package frozen forever just to make this proposition viable?
Debian server minimal, is kind of a "core Debian". There are netinst versions that can be even smaller. The Debian base image for Docker is even smaller than all that.
There is also an Ubuntu minimal install that you could call "core Ubuntu".
But more importantly, and I can't stress this enough: YOU CAN SWITCH DISTROS WITHOUT REINSTALLING. Might need to do some cleanup afterwards, but it's perfectly doable, more so between Debian based ones.
How do you do that? First time hearing this
What @exi@feddit.de said. Switching .deb based distros is little more than changing sources, maybe some pinning, doing an upgrade, and optionally a cleanup pass to remove any stranglers.
My main Linux box is a Debian-Ubuntu-Debian upgrade, that hasn't seen a proper reinstall for like 15 years (switched all the hardware several times, still no clean reinstall).
Switching between non-deb distros is also possible, with a chroot. Like, Gentoo to Fedora. As long as the kernel is compatible with the glibc, it's basically like running containers, just on slightly hard mode.
Replace Debian apt sources with Ubuntu ones, do system upgrade and install the Ubuntu-Desktop package, now you have Ubuntu.
It's been a while since I have done this, but it's totally possible.
We did this transition from Ubuntu to Debian at Work with thousands of workstations.
It requires a bit of time and testing but it's possible.
A minimal install like debian base already has a things that may differ from distro to distro. Or are you equating "distro" with window manager and GUI customizations? Even the kernel binaries may differ from distro to distro.
I know what I said. Linux upholds the "don't break userspace" contract pretty well: most kernels, particularly those from generalistic distros built with modules, are compatible with whatever userspace binaries you throw at them. Major version changes in glibc (or equivalent) is where incompatibilities start, but those happen quite rarely, and you can often still force multiple glibc versions to run side by side.