On Wed, 11 Jul 2012 15:27:41 -0400 Mike Gilbert <[email protected]> wrote:
> Personally, I think a consolidated systemd/udev package is the best > way to go here. A consolidated package means that: - every change made by udev developers would have to be reviewed by systemd team to make sure it doesn't break systemd. udev developers don't use systemd; - every change made by systemd developers would have to be reviewed by udev team to make sure it doesn't break openrc. systemd developers usually don't run openrc; - udev developers will force me to use eclasses they like and force their coding style on me; - i will force eclasses I like and my coding style on udev developers; - new udev wouldn't be able to be stabilized without systemd being stabilized at the same time (and I don't really think systemd is in any condition to go stable), - there will be a few random flags which will either work or not, depending on a state of magical switch flag, - and after all, the ebuild will be basically one big use-conditional. -- Best regards, Michał Górny
signature.asc
Description: PGP signature
