pulseaudio: module.c: module-detect is deprecated: Please use module-udev-detect instead of module-detect!

[Maarten Bosmans]

(just replying to an old message about this, please feel free to
forward it to the appropriate persons/lists in the freebsd community)

Well, I haven't seen any patches being send upstream to the pulseaudio
mailing list. That is a dissapointing result of my original message to
the freedsb-ports list. Please keep this in mind before complaining
again how bad pulse is on freebsd and how the developers are too
linux-centric and don't care aboud other unixes.

That being said, a 1.0 beta has just been released:
http://lists.freedesktop.org/archives/pulseaudio-discuss/2011-August/010796.html
http://pulseaudio.org/wiki/Notes/0.99
So this might be a good time to check what's needed to make it work
out-of-the-box on FreeBSD. I think the final 1.0 release is going to
be a couple of weeks from now, so there is some sense urgency needed
if you want to have your patches in before that.

Feel free to contact me directly through mail, through the
pulseaudio-discuss list or at #pulseaudio at freenode.

Maarten

2011/3/2 Michal Varga <varga.michal at gmail.com>:
> On Wed, 2011-03-02 at 16:34 +0200, Andriy Gapon wrote:
>> Greetings to the collective maintainers of the pulseaudio port :)
>>
>> What do you think about silencing the message in the subject line?
>> It looks like FreeBSD doesn't have udev and it is not coming, so there is no
>> module-udev-detect either.  Of course, something devctl/devd-based would be
>> useful, but until then the message is not useful, but simply annoying.
>>
>
> That change might go well along with this recent message:
> http://lists.freebsd.org/pipermail/freebsd-ports/2011-February/066081.html
>
> As I gather from it, upstream developers probably don't even have anyone
> running FreeBSD and I'd guess they aren't much aware of the issues
> pulseudio nowadays has here (after all, that deprecation warning being a
> good indicator).
>
> So instead of fixing things like these in ports, I'd say the issue
> should be reported/fix submitted to upstream, it's pretty much possible
> that they don't even know that there are systems that don't run evdev
> (note that I don't mean it offensively, more like speaking generally
> from experience, it simply happens).
>
> m.
>
>
> --
> Michal Varga,
> Stonehenge (Gmail account)
>
>
>