Re: ABI versioning

Hello Sean,

> I am working on packaging metakit for Debian, and I noticed that there
> is no SONAME in the default library provided. I was wondering what
> rules you guys have for ABI compatibility - will you not break ABI
> compatibiliy, or is the 4 in mk4 the ABI/API version?
>
> In other words, is there any easy way to tell when a new release of
> metakit will break programs that link against it dynamically?
> (recompilation is not an issue)

My aim is not to break MK compatibility in the 2.4.x series.

Versioning might be a good idea to introduce though. Main reason for  
not doing all that is that at the time I had no idea how to do proper  
versioning. There was less need then, when MK usually got linked in  
statically. Even now, it's less of an issue because it is linked in  
with the Tcl and Python extensions.

Thanks for doing this.

-jcw

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the "metakit" group.
To post to this group, send email to metakit <at> googlegroups.com
To unsubscribe from this group, send email to metakit-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/metakit?hl=en
-~----------~----~----~----~------~----~------~--~---