[Adium-devl] Protocol plugins

[Augie Fackler]

On Dec 31, 2007, at 4:08 PM, Evan Schoenberg wrote:

>
> On Dec 31, 2007, at 3:57 PM, Peter Hosey wrote:
>
>> On Dec 31, 2007, at 13:44:47, Evan Schoenberg wrote:
>>> There's a 'current' symlink which should be used rather than the  
>>> versioned folder.
>>
>> Presuming, of course, that the API doesn't change. Part of the  
>> problem is that *every* point release gets a new version folder,  
>> even if the public API is no different.
>>
>> I think providing a (let's say) 0.3 folder and keeping that through  
>> all the 0.3.x Libpurples would be a better solution. (Obvious  
>> exception for major API changes that prove necessary unexpectedly.)
>
> That's a great idea.  Since the libpurple versioning sanely based on  
> the consistency of its API, by definition all 0.3.x Libpurples are  
> intercompatible, and all 0.4.x or 1.y.z versions are probably  
> (though not necessarily, since it could be an incompatible API  
> change which isn't one used by the plugin) incompatible.

That's not how the framework maker is designed to work. If someone  
wants to beat me to this patch, then the thing to do is to make it add  
a 0.3 symlink that points to 0.3.1 ( and probably also a 0 symlink  
that points to 0.3 now, and would point to 0.4 when that comes out).

Does that make sense?

Augie