[mythtv] Ticket #6137: udevinfo has been replaced by 'udevadm info'
pebender at san.rr.com
Thu Aug 20 04:36:25 UTC 2009
Colin Guthrie wrote:
> 'Twas brillig, and Paul Bender at 19/08/09 02:30 did gyre and gimble:
>> Colin Guthrie wrote:
>>> 'Twas brillig, and Nigel Pearson at 18/08/09 23:53 did gyre and gimble:
>>>> 2) None of my Linux boxes have libudev, or DBus/HAL,
>>>> so I'm not personally keen to go in that direction.
>>> As time goes on it'll be harder and harder to avoid using libudev and
>>> dbus I'd reckon.
>>> Certainly the default audio system on pretty much all distros now
>>> requires libudev and dbus, so you'll be hard pushed to find a distro
>>> that doesn't support these packages and install them be default.
>> I do not include does not include libudev, DBus or HAL in MiniMyth.
>> For systems running as dedicated MythTV frontend appliances, there is
>> no need for libudev, DBus or HAL. For these systems, basic udev
>> functionality is more than sufficient.
> I can understand the argument for DBus/HAL here (HAL may have been
> useful to do automatic hardware detection/configuration and DBus was a
> dep of that but hardly needed for IPC etc. after that is over seeing as
> only one primary app is running!).
> But surely libudev is not going be overly controversial going forward? I
> mean it's part of udev now. It's part of the same source package. You'd
> actually have to go out of your way to exclude it from a modern system.
> I personally don't think trying so hard to exclude it is worth the
> effort to save ~60k of space!
I have no objection at all to libudev. After all, stripped it is less
than 40k (no to mention that it only adds 16k to the squashfs image) and
it does not come with additional configurations and daemons that are not
already required for udev operation. At the moment is it not included
because nothing depends on it, which I suspect is due to the fact that
it is relatively new.
More information about the mythtv-dev