The eudev project launches

This is a real nice argument; except maybe for the part that you wouldn't be forced to think and make the patch nor maintaining it working (you could shift the responsability that half of the test matrix to the other, more interested, part). Your thing, when a patch like that comes, would be to overlook it, apply it, test *your* side of the test matrix and voilà.

> And yeah, I have no interest in maintaining such a beast, especially since it makes our life harder and gains us nothing.

This is the Most Honest part of your argument. "I am not in the mood, MY code (the code I have to look at from time to time) will get uglier, and it's mine, so I won't do it."

> Anyway, calling us pathetic, and five-year olds also doesn't really make use take you seriously.

Let's be honest here: I called BOTH sides of the discussion pathetic five-year olds; if you can't re-read this whole discussion, take a little distance and see how it is funny, I hate to tell you but you could use some sense of humour. I don't want to be taken seriously -- I want you (and by you, again, I mean both sides of this discussion) to perceive no one is really taking you seriously when you start bickering and sidetracking and trhowing tantrum fits. And this (bickering/sidetracking/tantrums, not being seen as serious) is a BIG loss to the Free Software Community as a whole; so you might want to consider that...

> Also, to clarify one thing: I don't really care whether somebody forks udev, quite frankly I am quite happy if they do so that they can deal with people like felipec, barbato or rulgard, and I don't have to. What I am annoyed about though is the FUD and falsehoods they spread while doing so. Most specifically their constantly repeated claim that udev upstream wouldn't allow non-initrd with /usr split off, even though we each time point out that udev doesn't care and it's other software that will break, not udev.

That is Ugly and Wrong. And that is the pathetic five-year olds part for the other side of the discussion.

Free Software does not need a REASON to be forked: the answer to "we have a team of developers and some infrastructure, we think we could do better maintaining this" is "Good! Be my guest! If it's copyleft, just distribute the source and all is well, maybe you will do a good job and I will use your commits here too!"

> But anyway, I'll leave it at this. It's unlikely I'll change you mind on things, and quite frankly you are not really succeeding to change mine either...

I never intended to change your mind. Even if I don't personally like systemd -- for the reasons I stated elsewhere in this thread, I admire your hard work and I am thankful for it. I just wished (before) that you were more accomodating, but you are not up to it, and there is nothing I can do about it. Now, eudev is a reality, and we all continue to win.

Maybe you should have a look at the Linux kernel. It's probably the most configurable project that ever existed. The kernel has matured where we don't have lots of #ifdef HAVE_xxx in the .c sources. We do put them into the .h files, where a static inline may act differently depending on the configs set. It's actually quite an elegant solution.

I based my Makefile for trace-cmd and kernelshark partially off of the Linux kbuild system. It's much more versatile and easier to understand than autoconf. I should work on making the kbuild system available for other projects as well. Package it up and reuse it.

Yes, we don't test all the different config options either, but you test what you ship. If someone finds a set of options that break, it's not that difficult (or time consuming) to fix it. I know this from experience as well.

I left off 'c)' because it was entirely an opinion, and not a technical issue at all.