[vlc-devel] Future of the update mechanism

Jean-Baptiste Kempf jb at videolan.org
Thu Jul 30 18:59:27 CEST 2009

On Thu, Jul 30, 2009 at 05:44:42PM +0200, Rafaël Carré wrote :
> Let me summarize the different solutions:
> 1/ Let the user check regularly www.videolan.org and install himself
> latest version.
>   pros: no code, no bugs
>   cons: more bug reports from people using old versions
> 2/ Use Sparkle on OSX
>   pros: bugs in Sparkle are dealt by the Sparkle team
>   cons: OSX specific, additional server CPU load and $ spending if SSL
>   is used, but we can use DSA signatures
> 3/ Use the current code present in src/misc/update.*
>   pros: already present, could get a bit of love from myself
>   cons: integration into the GUI(s) is error-prone (a bug in OSX GUI it
>   prevented updates from 1.0.0 to 1.0.1, and from 1.0.1 to future
>   releases) and should be reviewed
> feel free to correct/enhance this mail

4/ Do like 3/, but just say a "Hello, new version available, click HERE
to get it, and let the browser/proxy manage it.

Best Regards,

Jean-Baptiste Kempf

More information about the vlc-devel mailing list