ABI report for Vermillion Devel 63

[Laszlo (Laca) Peter]

On Wed, 2007-04-11 at 22:14 +0200, Alvaro Lopez Ortega wrote:
>  >   Function removal can be a serious ABI issue. If the function was
>  >   previously exposed in the module's header files then it is an issue
>  >   and the GNOME community should be informed [NOTE: 'how' to notify is
>  >   not known]. One easy way to determine this is to search an old version
>  >   of the package for the offending header file.
> 
>    I made those changes. That patch is not in the community repository
>    yet, so by the moment we are the only ones who are using it.
> 
>    Anyway, being an evolving library it isn't such a big deal, is it? 

Breaking the ABI of an Evolving lib _is_ a big deal.
Fortunately this is only in vermillion-devel, but if it was,
we would have to keep the ABI compatible.

We had a similar issue with Erwann's multihead patch, which
was included in Solaris before it was fully accepted upstream
and the final API was different.  Now we have to live with
gtk+-09-solaris-2.0.0-compat.diff.

Laca