On Tue, Oct 11, 2011 at 11:44 PM, Dan McGee <dpmcgee@gmail.com> wrote:
This is really f***ing stupid of upstream.
Unlikely.
Why are they doing this outside of simply wanting to break everything?
What is breaking?
I'm not a fan of this as we are making upgrades way too fragile,
How? We always require udev, initscripts and mkinitcpio to be in sync, running udev should not be affected.
not to mention moving what is very clearly a *binary* into a non-binary path, which is totally bogus.
There are plenty of binaries in libexec (and there are plenty of non-binaries in bin), I don't see the problem.
I know I've done `killall udevd && udevd --daemon` before to get the new version running; sounds like this is not going to work at all anymore.
That does not sound like a good idea, you'll at least lose events.
I would honestly pester upstream and have them justify the color of their hat this week;
Unless you can come up with some real problems caused by this, I think that would be a waste of time. Even if they did not explain their reasoning very well this time, I'm pretty sure they have some, and won't revert just because some random people say "I don't like it".
-1 from me on this whole change, upstream decision or not.
-1 on what? What exactly are you proposing? -t