[Android-tools-devel] Android N source code now available

[Hans-Christoph Steiner]

Hey seamlik,

thanks for this awesome write-up!  All in all, it looks like 7.0 will
make things a bit easier.  Having only one ~stage1 package to deal with
definitely reduces the work a lot, and makes security updates easier.
I'm definitely on board for getting 7.0 into stretch.

.hc

殷啟聰:
> Hi Chirayu,
> 
> Surprised that the tags are pushed in just several days! :)
> 
> Now that the source codes are there, maybe we can finish updating all
> packages to 7.0 before Stretch freeze (Q3 2016, or 5 November? See
> <https://wiki.debian.org/DebianStretch>). So far I can think of
> several changes to the packages, albeit the overall packaging won't
> change too much:
> 
> Removal of pkg:android-platform-build-headers
> =============================================
> 
> Since Android 7, "AndroidConfig.h" have been removed (see
> <https://android.googlesource.com/platform/build/+/43146118aab8e15e8ed4f859106d8ddccc06d21b>).
> Judging from the Git log, looks like AOSP guys have been planning to
> get rid of these files for a long time. Now that these files are
> removed, pkg:android-platform-build-headers can be removed as well,
> and all other packages should stop including these headers. Thus, we
> can also get rid of the circular dependency between
> src:android-platform-build and src:android-platform-system-core. As a
> result, src:android-platform-build no longer need to have staged
> upload.
> 
> Separation of AIDL as an Independent Package
> ============================================
> 
> Since Android 7, AIDL is separated as an independent project
> <https://android.googlesource.com/platform/system/tools/aidl>. AIDL in
> Android 6 does depend on any libraries, so it will be relatively easy
> to deal with. The tricky part is the transition in Debian.
> 
> Currently AIDL is built in src:android-platform-frameworks-base and
> used by src:android-platform-$version. We can remove the AIDL package
> in src:android-platform-frameworks-base and upload it, then upload
> src:android-platform-system-tools-aidl, then the rest are fine.
> 
> Time to Re-enable ARM Builds!
> =============================
> 
> A guy from Debian LAVA complained about removing ARM builds of ADB and
> fastboot at the removal bug <https://bugs.debian.org/817823>. And I am
> also thinking about buy ARM laptops in the future, it would be a great
> pity if Android Tools won't be available on those platforms. Chirayu
> has been using ARM64 Debian, he can help as well.
> 
> We gave up the support of ARM and MIPS builds because libbacktrace
> FTBFS on MIPS and libunwind FTBFS on ARM64. Several hours ago I fixed
> the FTBFS of libunwind, and it already build fine on armel and armhf,
> why not build them? Now I have setup ARM and MIPS QEMU environments on
> my machine, and buildd builds all architectures for us, it won't be a
> burden to support them.
> 
> If we don't enable the builds for ARM and MIPS for the reason that
> "Google officially supports the SDK on x86", well we can't really
> enable the amd64 build either because Google only officially supports
> the SDK on 32-bit x86.
> 
> We still won't consider building the SDK on other architectures like
> PowerPC or Sparc because Google only supports the Android system on
> x86, ARM and MIPS, and libunwind doesn't have the corresponding source
> files on other platforms and therefore can't be built.
> 
> Looking forward to seeing Android SDK on MIPS. Android SDK on ARM and
> MIPS, this is one of the attracting points of android-tools in Debian!
> 
> Cheers,
> Kai-Chung Yan
> 
> 2016-08-23 23:57 GMT+08:00 Chirayu Desai <chirayudesai1 at gmail.com>:
>> Hi everyone,
>>
>> Android Nougat 7.0 (API Level 24) has been released, and the source code
>> is now available.
>>
>>  * [new branch]            nougat-release -> nougat-release
>>  * [new tag]               android-7.0.0_r1 -> android-7.0.0_r1
>>
>> Ideally, we would update all the packages to 7.0.0, and also create a
>> new android-framework-24 package. Need to take a look at the sources to
>> see what's changed, sycning right now.
>>
>> Having a proper plan in place would be helpful. A bit of this was
>> already discussed on another thread (RFS
>> android-system-core/1:6.0.1+r55-1), regarding the upload order of
>> packages after the update.
>>
>> Cheers,
>>
>> Chirayu Desai
>>
>>
>> _______________________________________________
>> Android-tools-devel mailing list
>> Android-tools-devel at lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel
> 
> 
>