603 karma · joined April 19, 2021
>to force other distributions into using libsystemd, which would logically end with them also using systemd itself.
As I said elsewhere, libsystemd is just a library with some generic functions provided for convenience. This is like saying that installing python libraries on your system logically means that the PSF is trying to take over your system and forcibly rewrite everything in python, it doesn't make any sense.
For utilities that have to interact with low level kernel APIs it's even worse, every library seems to have to reimplement their own parsing of various other random things like netlink, or in the various pseudo filesystems like sysfs, procfs, cgroupfs, etc etc, the situation is really way out of hand. I don't know how to solve this in a reasonable manner beyond what systemd is already doing. Yes people will complain that they have a systemd dependency now but what else can you do? This is the exact reason the BSDs update the kernel, libc, init and core utils in tandem and consider a lot of the kernel API to be private, Linux was just slow to catch on in that regard.
I believe the reason for eudev is to avoid some of those other unwanted changes from upstream udev that broke udev scripts. Which to me is a fine technical justification, but not really related to another udev implementation having a build dependency on libsystemd. The udevd package seems maintained so I really don't understand what operational issues that comment is getting at.
This is not correct, I don't know where you got this idea. The systemd-udevd daemon still runs without systemd. The code has moved into the systemd repository, and it has a build dependency on libsystemd, but otherwise it has no runtime dependency; your distro should be able to package it separately if it wants.
To me that it always the problem that has faced any minority groups anywhere -- it's never obvious to the majority what the alienating behavior is. So they have to painstakingly explain it, and of course some of them will always get accused of overreacting and attacking the majority. What else can be done?
It's really difficult to continue this conversation if you view the concept of justice to be alienating, what is open source if not a means to deliver code to large groups of people who would otherwise be alienated from working with that code? I don't understand. If you're not interested to help customers and be fair and just to them, I would think you would have a hard time working at any company. What is your real goal?
Usually I see good community managers as people who go out of their way to be agreeable to the whole community, helping to reach common ground and consensus. That's their job, to solve those people problems. The size of the circle is whatever your community defines it to be, for some communities it's obviously easier to find consensus than for others. Example from the reddit post: Linux people seem to be fine with both GPL and BSD license, but BSD people seem to view GPL as problematic. So practically speaking it seems it can be easier to reach consensus in Linux, around some particular code licensing issues anyway (Please don't start a flamewar about this, I personally don't take any sides here when it comes to licensing).
For two, when the word is used in the context of inclusivity, usually the problem is that someone is behaving in a way that's exclusionary -- it's not being nice to encourage them to continue that behavior.
I also wouldn't say that that runs contrary to the GuixSD philosophy, as there are a lot of packages in Guix that are written in C and C++ and other compiled languages, and I don't believe they plan to replace them. Maybe I'm wrong about that? At some point it might be interesting to have a Lisp/Scheme-only distro. Of course the kernel would still pose a problem there.
I think it would be worth asking if they could keep that libgtk_static around, for users who know what they are doing. Make it very obvious you are not creating extra burden on them for just your use case. The problem with an option to build and install is that it makes it so they have to support static linking in lots of other use cases, which it doesn't seem they want to do.
I'd be interested to hear if static linking GTK even has that many benefits. From what I have seen, the library may not play so well with LTO.