News for hackers. Stuff that matters.
Re:Portable systemd services by oblio on Thursday November 17, 2016 @04:21AM (#12975817)
If no one will say it, I will: it's stupid that we have multiple package managers and package formats.

There's no fundamental technical reason Linux couldn't have just 1 extensible package format and 1 extensible package manager. All the reasons for the split are social ("I like A"), political ("we want to be able to control A") or historical ("A came first, we built our house on A, we can't abandon A").

Re:Portable systemd services by majewsky on Thursday November 17, 2016 @07:54AM (#12977003)
The historical argument might be the biggest one, from my own experience with the steaming pile of shit that is RPM: https://blog.bethselamin.de/posts/argh-pm.html
Re:Portable systemd services by oblio on Thursday November 17, 2016 @10:16AM (#12978101)
I actually recently took a much shallower dive through RPM than yours (http://blog.oblio360.com/2016/08/23/rpm-install/). I knew that RPM was not that loved as a format, but what you've described there truly is "insane" (I know that you used that word many times in the article, but it fits the situation).
Re:Portable systemd services by digi_owl on Thursday November 17, 2016 @11:17AM (#12978724)
Really makes one wonder why RH is still allowed to set the direction of Linux as a whole. Oh wait, money...
Re:Portable systemd services by legulere on Thursday November 17, 2016 @06:24AM (#12976433)
Even with the same package managers, packages are still incompatible from different repositories because of differing assumptions about the underlying system and differing packages for the dependencies.

Converting between the differing package formats is actually relatively easy and tools like `alien` exist, that do that.

Re:Portable systemd services by oblio on Thursday November 17, 2016 @08:30AM (#12977223)
I know about that, I actually hate those "underlying system" differences even more. With a bit of forethought we could have covered all the use cases and not have silly things such as /etc/redhat-release vs /etc/debian_version.[1] There's no reason we couldn't have had a "/etc/distro-info" with a standardized format for writing down the distro name, the platform and the full distro version (branch/release, minor release, revision, build number, etc.). And there's thousands of these differences.

As I said: social/political/historical reasons bringing us down.

[1] I know about lsb_release, but that's an example of an afterthought, not a part of the initial design.

Re:Portable systemd services by vamega on Thursday November 17, 2016 @09:38AM (#12977771)
"/etc/os-release" is present in most newer releases. Sounds exactly what you want from "/etc/distro-info"
Re:Portable systemd services by oblio on Thursday November 17, 2016 @10:13AM (#12978068)
Whaddayaknow, I missed that file. Apparently it's a Freedesktop standard (https://www.freedesktop.org/software/systemd/man/os-release....).

My point still stands, something like this should have been included from the first releases of Linux distros, 20 years ago. And that was just a random example I came up with after 2 minutes of trying to prove a point. There's many, many more like it.

Also, just for kicks I took at look at the spec and...

1. ANSI_COLOR is funny:

> A suggested presentation color when showing the OS name on the console. This should be specified as string suitable for inclusion in the ESC [ m ANSI/ECMA-48 escape code for setting graphical rendition. This field is optional. Example: "ANSI_COLOR="0;31"" for red, or "ANSI_COLOR="1;34"" for light blue.

2. And some parts are scary:

> parameters may be set using os-release

Oh-oh! Everything is optional! That's really bad for a RFC.

Re:Portable systemd services by qznc on Thursday November 17, 2016 @04:27AM (#12975845)
Why do have so many programming languages? Because they fulfill different needs. C and Python are used for different things. Yet, there is overlap, which creates a constant tension. When do you rewrite your Python module into C for better performance?

Likewise, different packaging formats exist for different needs. Docker and Ubuntu Snap are for different needs, yet they overlap. Systemd did initially not care about packaging and containers. Yet, there is an overlap, like "How to do logging?". Docker and Systemd both grow and overlap more and more.

Re:Portable systemd services by oblio on Thursday November 17, 2016 @04:32AM (#12975870)
We're talking about different things here. deb/rpm serve the same role. yum/apt ditto.

We have gratuitous differences which could have been prevented with a better design. See for example even the mess in the rpm world where a SUSE rpm may or may not work on Red Hat.