[Android-tools-devel] RFS: android-platform-external-libunwind/6.0.1+r55-1

[Markus Koschany]

On 01.08.2016 20:53, Hans-Christoph Steiner wrote:
> 
> For Android-Tools packages, we need to do packaging updates to make sure
> the versions are all in sync.  Like Chirayu said, the Android SDK
> packages all need to be built against the exact same version since
> that's how upstream builds it, and the libraries and headers are not
> versioned at all.  In order to keep this manageable, that means
> occasionally pushing packages where we are bumping the upstream version
> even though the upstream source only has a different version.

Then our current updating process is obviously flawed because there
shouldn't be any difference in building against version 1.0 or 1.1
provided both versions are identical.

> If we try
> to manage packages with a range of upstream versions to avoid these
> updates, it'll be only add to the management nightmare we already have.

I guess I need a concrete example to understand the management
nightmares. I'm quite sure that this is easily solvable.

> This only affects internal Android SDK packages.  The user facing
> packages almost always have updates when the upstream version changes.

In my opinion it doesn't really matter if we divide packages into "for
internal use" or "user facing" packages. They are all part of Debian and
the same guidelines and rules apply everywhere. That would be just a
waste of disk space on snapshot.debian.org. The version number really
can't be the decisive argument why a package can be built or not.

Regards,

Markus

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