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

Julien Cristau jcristau at debian.org
Wed Aug 19 21:23:21 UTC 2015


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: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/android-tools-devel/attachments/20150819/46543067/attachment.sig>


More information about the Android-tools-devel mailing list