[vlc-devel] Future of the update mechanism

Rémi Denis-Courmont remi at remlab.net
Fri Jul 31 08:49:26 CEST 2009

On Thu, 30 Jul 2009 14:17:18 -0700, "Pierre d'Herbemont"
<pdherbemont at free.fr> wrote:
> Are you trolling?

No. I'm just pointing out the truth, which is that Windows support is
falling almost entirely onto the Linux developers, both when it makes sense
(Qt4, partly contribs), when it makes no sense but there are no
alternatives (core) and when it would make sense to have it handled by OS X
developers (update code, and partly contribs).

Since it's volunteer-basis, I can perfectly understand that you're not
interested. In fact, I understand it all the better as I have grown rather
fed up with trying to work around the Win32 specifics whenever extending
the LibVLC core.

But we need to have consistent policy. Either anyone is free to break
"other" platforms. And then I will eagerly stop bothering to implement
Win32 back-ends for whatever I'm doing. Or he who "breaks" a feature shall
fix it. And then, he who implements Sparkle shall ensure that the update
code still works on Win32. *Frankly*, I am fine either way, but not with a
third way.

Rémi Denis-Courmont

More information about the vlc-devel mailing list