[Pkg-parrot-devel] New version of parrot package is in mentors

[Allison Randal]

On 04/06/2011 08:18 AM, Dominique Dumont wrote:
> The point between soname and package name is explained there:
>
> http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-
> runtime
>
> So the actual question (for Allison) is:
> - will next parrot lib release have  symbols removed or with changed signature
> since 3.0.0 ?
>
> If not, the soname of libparrot should not change and the libpackage name
> should not change.
>
> That said, having '3.0.0' in the package name will lead to confusion. Hence
> Kyle's suggestion to have only '3' (or may be '3.x') in the package name.
> All depends on the evolution of libparrot ABI.

The history of Parrot's backward-incompatible ABI changes is tracked in 
the git repository:

https://github.com/parrot/parrot/blob/master/PBC_COMPAT

This demonstrates that there were incompatible changes in the 3.0.0 release.

In general, Parrot has a deprecation policy on ABI changes, which is 
that they must have been announced in the previous stable release (in 
the file api.yaml). This means any stable release is allowed to add or 
remove symbols, as long as proper notice was given in the previous 
stable release. So, yes, we'll need to keep the full version number in 
the name.

Allison