[Android-tools-devel] Fwd: Re: Bug#790978: android-platform-build: library transition may be needed when GCC 5 is the default

[Hans-Christoph Steiner]

Julien makes a point here about why we should keep the .so versioning, even
though we need to update to new versions all android-platform* packages at the
same time. The .so versioning provides another way to enforce that all android
packages are at the same version.

.hc


-------- Forwarded Message --------
Subject: Re: Bug#790978: android-platform-build: library transition may be
needed when GCC 5 is the default
Date: Wed, 19 Aug 2015 23:23:21 +0200
From: Julien Cristau <jcristau at debian.org>
To: Hans-Christoph Steiner <hans at eds.org>
CC: Simon McVittie <smcv at debian.org>, 790978 at bugs.debian.org

On Wed, Aug 19, 2015 at 13:14:18 +0200, Hans-Christoph Steiner wrote:

> All of the android-* packages must be updated to the latest version at the
> same time.  It is more unpredictable to have android-* packages at different
> upstream versions since no one is running that configuration, and upstream
> does not do anything to support that (e.g. no versioned ABI, etc).  Therefore,
> the ABI is guaranteed to be compatible since they'll all be built together.
> 
> In practice, this means that the process of updating to the latest upstream
> version has to start from the most core packages, then progress to the ones
> that depend on it.
> 
> That said, this private shared library arrangement allows for security patches
> in the android shared code to be applied without having to rebuild everything.
> 
It does require that you version your dependencies appropriately,
though, so that a non-working combination is not installable.

Cheers,
Julien




-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/android-tools-devel/attachments/20150820/c5aa499a/attachment.sig>