[Adium-devl] Synchronizing with libpurple

[bgannin]

On May 29, 2007, at 12:08 PM, Ryan Govostes wrote:

> Evan wrote,
>
>> Given the number of bugs which get fixed with each release and the
>> advantages of knowing the our libpurple framework matches the
>> current release (for coordinating bug reports and coding efforts),
>> a policy of following libpurple releases where possible could make
>> good sense.  Thoughts?
>
> I think this does make sense, but then again I love bleeding edge
> things even when I get cut, e.g. I subscribe to Trac commits via RSS
> and build a new version of Adium a few times a day.
>
> Libpurple is a separate framework, right? Maybe it would be possible
> to use the auto-updater to download just a new libpurple.framework
> and back-up the old version. That way in between Adium releases
> people can upgrade their libpurple (if there is reason to do so), and
> if new problems arise they can just revert to a previous 'stable'
> version.

Just because it may be a separate framework does not imply API or  
feature parity. With any given update underlying parts may change in  
a way that exposes a new issue in previously fine code, creates an  
entirely new issue, or much more. This may not be the case, but its  
certainly a possibility. Moral of the story - being a framework (and  
if I recall correctly, we actually build the framework manually, not  
just 'get' it from Pidgin) doesn't mean you can assume a 1:1  
relationship at any time allowing replacement. Updating a core  
component requires a proper QA cycle to vet any breakage that may  
occur and shouldn't be foisted on the user to do so.

- brian 'bgannin' ganninger

>
> Regards,
> Ryan Govostes
>
> _______________________________________________
> Adium-devl mailing list
> Adium-devl at adiumx.com
> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com
>