<div dir="ltr">Here is a start for the package android-google-platform-installers[1] which generate installers for platform 24, 23 and 22 (I think it's easy to add older platforms). I will try to improve this even more following the suggestions and discussions we had.<div><br></div><div>[1]: <a href="https://github.com/Aallam/debian_google-android-platform-installers">https://github.com/Aallam/debian_google-android-platform-installers</a> </div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><i>Mouaad Aallam</i></div></div></div>
<br><div class="gmail_quote">On Tue, Jul 19, 2016 at 9:59 PM, Hans-Christoph Steiner <span dir="ltr"><<a href="mailto:hans@at.or.at" target="_blank">hans@at.or.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
I think making the source package use a python or perl script to parse<br>
the Google repo XML makes sense. Then we can just build the source<br>
package, and it would generate all of the latest binary packages needed.<br>
<br>
I'll let Mouadd take the lead on this one since he's been doing the work<br>
on it so far.<br>
<br>
.hc<br>
<br>
Chirayu Desai:<br>
<div class="HOEnZb"><div class="h5">> On Mon, Jul 18, 2016 at 8:40 PM, Hans-Christoph Steiner <<a href="mailto:hans@at.or.at">hans@at.or.at</a>> wrote:<br>
>><br>
>> I thought about enabling `android update sdk` in the Debian package's<br>
>> version of `android`, but now I'm thinking that it would be better to do<br>
>> it all with Debian packages. I think a primary use case of the Debian<br>
>> packages will be to set up a system to build Android apps in an<br>
>> automated way (e.g. via Chef, Puppet, Ansible, CI script, etc). It'll<br>
>> be a lot easier to do that if all of the components of the SDK can be<br>
>> directly `apt-get install`ed. `android update sdk` is a really crappy<br>
>> package manager, and I've spent quite a bit of time fighting with it<br>
>> when automating things like CI builds.<br>
> I would agree here. It shouldn't take long for us to add the newer<br>
> versions to the contrib packages (for future releases)<br>
>><br>
>> I think it could make a lot of sense to have a single<br>
>> google-android-platform-installer source package that then makes<br>
>> multiple google-android-platform-*-installer binary pacakges for each<br>
>> platform number. It might even make sense to have a single source<br>
>> package for all of these installer binary packages. The source package<br>
>> would just contain basically a template, then the build process would<br>
>> generate lots of binary packages based on replacing things in the<br>
>> template using a list of values for all of the Google binary packages<br>
>> that we want to support, e.g.<br>
>><br>
>> * docs<br>
>> * platform-*<br>
>> * sys_img-*<br>
>> * build-tools-*<br>
><br>
> I'm working on creating the google-android-platform-installer package right now.<br>
> Experimenting reading up a bit on how to best use templates, and<br>
> things like deb-substvars.<br>
> A single source package for all the google binary packages could work<br>
> too. Maybe we could even have something which parses the repository<br>
> xml, and creates packages for things we want. Not sure if we want to<br>
> do XML parsing though. If we do though, I have some past experience<br>
> with python which could be helpful.<br>
><br>
> I can continue with the platform-installer package, or get started<br>
> with a generic google binary downloader, whatever suits us the best.<br>
><br>
>><br>
>> .hc<br>
>><br>
>> Chirayu Desai:<br>
>>> Hi,<br>
>>><br>
>>> This idea sounds good, and should make us able to have an android app<br>
>>> building shortly.<br>
>>> The "proper" SDK could come later, lots of work to do there still.<br>
>>><br>
>>> There's one thing which has discussed at DebConf (informal<br>
>>> conversation at some random place) - what we could do is use the<br>
>>> components we have building and working currently right now, and then<br>
>>> grab the rest from google / use contrib packages. However, it might be<br>
>>> tricky to combine files from multiple packages, I hadn't really<br>
>>> thought about that before. Still putting this thought here, if it<br>
>>> turns out to be helpful.<br>
>>><br>
>>> One more thing, do we want to have some sort of integration with the<br>
>>> SDK Manager ('android' command) and debian packages? I.e., user can<br>
>>> pick SDK platform 23 and get the platform package Mouaad created<br>
>>> installed. If he picks emulator, he can get the emulator images<br>
>>> downloaded directly from Google if they're not in a debian package. It<br>
>>> would involve some code changes though, but I'm not sure exactly how<br>
>>> much work would that be, and if it would be worth it to do that right<br>
>>> now for the installer packages.<br>
>>> It could still be useful later though, when we have platform packages<br>
>>> built from source.<br>
>>> And either way, part of this was discussed earlier as well, where the<br>
>>> user should still be able to install his own packages / add custom<br>
>>> stuff / install the missing packages from Google easily in a way that<br>
>>> works with the existing debian packages.<br>
>>><br>
>>> I'm just getting back to work after the DebConf trip, lots of catching<br>
>>> up to do - I did read all of the e-mails when there, just didn't get a<br>
>>> chance to send a proper reply until today.<br>
>>><br>
>>> Regards,<br>
>>> Chirayu Desai<br>
>>><br>
>>> On Tue, Jul 12, 2016 at 11:15 PM, Mouaad Aallam <<a href="mailto:mouaad@aallam.com">mouaad@aallam.com</a>> wrote:<br>
>>>> A start package for Google Android SDK Platform 24[1]<br>
>>>><br>
>>>> [1]: <a href="https://github.com/Aallam/debian_google-android-platform-24-installer" rel="noreferrer" target="_blank">https://github.com/Aallam/debian_google-android-platform-24-installer</a><br>
>>>><br>
>>>> Mouaad Aallam<br>
>>>><br>
>>>> On Mon, Jul 11, 2016 at 4:29 PM, Mouaad Aallam <<a href="mailto:mouaad@aallam.com">mouaad@aallam.com</a>> wrote:<br>
>>>>>><br>
>>>>>> This approach would make the packaging simpler, but I think we would<br>
>>>>>> provide a much better experience to users who are installing the<br>
>>>>>> platforms if there was one Debian package per platform package. That's<br>
>>>>>> how the platforms are represented using the `android list sdk` command<br>
>>>>>> line tool, and the `android` GUI package installer. That's what Android<br>
>>>>>> devs are used to.<br>
>>>>>><br>
>>>>>> I think it also provides a more Debian-ish experience, I need X so I do<br>
>>>>>> `apt-get install X`.<br>
>>>>><br>
>>>>><br>
>>>>> Alright then, that was just an idea I had :D, let's do it the way you just<br>
>>>>> discribed then.<br>
>>>><br>
>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> Android-tools-devel mailing list<br>
>>>> <a href="mailto:Android-tools-devel@lists.alioth.debian.org">Android-tools-devel@lists.alioth.debian.org</a><br>
>>>> <a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel</a><br>
>>><br>
>>> _______________________________________________<br>
>>> Android-tools-devel mailing list<br>
>>> <a href="mailto:Android-tools-devel@lists.alioth.debian.org">Android-tools-devel@lists.alioth.debian.org</a><br>
>>> <a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel</a><br>
>>><br>
>><br>
>> _______________________________________________<br>
>> Android-tools-devel mailing list<br>
>> <a href="mailto:Android-tools-devel@lists.alioth.debian.org">Android-tools-devel@lists.alioth.debian.org</a><br>
>> <a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel</a><br>
><br>
> _______________________________________________<br>
> Android-tools-devel mailing list<br>
> <a href="mailto:Android-tools-devel@lists.alioth.debian.org">Android-tools-devel@lists.alioth.debian.org</a><br>
> <a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel</a><br>
><br>
<br>
_______________________________________________<br>
Android-tools-devel mailing list<br>
<a href="mailto:Android-tools-devel@lists.alioth.debian.org">Android-tools-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel</a><br>
</div></div></blockquote></div><br></div>