Alexe Stefan <stefanalex...@gmail.com> writes:

> Upstream, it's maintained.

See my other emails for an explanation of why looking at a commit graph
is not good enough to tell if something is maintained.

> Downstream, 2 people volunteered.

And proposed ugly 'fixes' (read: hacks).

> So it is maintained.
>
> The incompatibilities are for some desktop specific situations, and
> there is a pr upstream(hacky, but work in progress).

No they aren't.  The APIs eudev is missing (and stubs now) are not in
any way specific to desktop.  I also don't buy that desktop-server
dichotomies exist.

> For servers, or minimal desktops(which is what I expect gentoo is
> mostly used for), eudev is fine.

Sorry, I don't buy that an out of date fork with unfixed known bugs that
regularly trails behind with the hwdb is 'fine'.  Especially when said
fork has no improvements.

The only reason I see to use eudev is 'I prefer it out of principle'.
This is an okay reason, but it *does not* outweigh QA concerns.  As I
said before, if those were to go away, which would be most simply
achieved by reforking up-upstream there would be no reason to omit eudev
anymore, and eudev would hence be back.

I know this is viable since I already tried to do so in order to keep
eudev alive because I expected this ruckus would happen, but nobody
aired interest, and my time to waste is scarce, so I dropped the project
and started using systemd-utils[udev].

In the meanwhile, while the two downstream volunteers address that, an
::eudev overlay can be established.  As I went over in another email I
posted to this thread, it should not be particularly difficult to
implement or maintain (nowhere close to LibreSSL, for instance, as eudev
didn't diverge nearly as much as LibreSSL did, and since
virtual/{lib,}udev exist).

My last refork attempt involved a git-filter-repo based script which
reformatted the systemd repository into one that could be git-merge'd
into a tree with a build system.  This worked, and it would be easy to
keep up-to-date, but I never finished it.

Hope to review your contributions upstream soon, have a lovely day :-)
-- 
Arsen Arsenović

Attachment: signature.asc
Description: PGP signature

Reply via email to