As for systemd, why is it that the GNOME project feels that mandatory dependence on such features is necessary when the KDE project does not? The KDE project seems to have no trouble writing cross platform compatible code. The only instance in which KDE fails to be cross platform involves Network Manager, which is Linux specific. As far as I know, Network Manager is developed primarily by RedHat employees. They seem to only care about Linux (and quite possibly, only RedHat's version of it). This causes headaches for us because Gentoo encompasses more than just Linux. Unfortunately, our teams dedicated to non-Linux things lack the man power necessary to address that issue.
With that said, Gentoo has its own cross platform solution called OpenRC that runs on top of sysvinit. I do not think that we would be having this conversation had OpenRC been incorporated into Fedora instead of Upstart.
With that said, I do not think RedHat gives Oracle much opportunity to contribute to RHEL development. That could change if RedHat were to adopt Canonical's practices of giving commit privileges to people outside their organization and having an open bug tracker.
okay, I already tried this once, but this is way off into the weeds, and I'm not interested in a bash fest. either we get back on the topic of udev or I'm out.
As an additional note, I am putting the finishes touches on the kmod work. There are a few additional things that I want to address, but it will be back in HEAD soon.
Yes, I know it "would make GNOME Linux only", but there are some points to consider:
1) Isn't that the de facto case already?
2) The dependency is IIRC on the systemd interface, meaning that you can replace it with other software that provides the same functionality.
And while I'm grateful for the work Canonical has put into making Linux a 'mainstream' desktop possibility, there's no comparing Red Hat's and Canonical's contributions to the Linux ecosystem, Oracle doesn't even register.