<div dir="ltr">Hello,<div><br></div><div>I've done an example of two packages[1][2] using a shared debconf template mechanism (which can be applied to other installers).</div><div>it works as following:</div><div><br></div><div>- First installed package will prompt a frontend asking the using to pick a mirror (the debconf template name is `google-android-installers`)</div><div>- The package will be installed and all future google-android-*-installer packages will add themselves as users of the template google-android-installers.</div><div>- Removing a package will unregister the package from the template. when the last package unregisters the template `google-android-installers` is removed. </div><div>- To change the value of the `google-android-installers` we can simply dpkg-reconfigure a google-android-*-installer and the frontend will prompt asking for choosing a new value.</div><div><br></div><div>[1]: <a href="https://github.com/Aallam/debian_google-android-platform-23-installer">https://github.com/Aallam/debian_google-android-platform-23-installer</a></div><div>[2]: <a href="https://github.com/Aallam/debian_google-android-platform-24-installer">https://github.com/Aallam/debian_google-android-platform-24-installer</a></div><div><br></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 Thu, Jul 14, 2016 at 3:31 PM, Chirayu Desai <span dir="ltr"><<a href="mailto:chirayudesai1@gmail.com" target="_blank">chirayudesai1@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
As discussed on IRC #debian-mobile<br>
<span class=""><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>
</span>24 is android N, which isn't currently fully available.<br>
The final SDK is out, which is why we can have the platform package here.<br>
However the source code is not, and won't be until after the final<br>
release, which is supposed to be sometime in August / September.<br>
Also, we won't really be able to test apps made for API 24, as it's<br>
currently only available in the form of developer preview for a select<br>
few devices.<br>
<br>
23 is also what we have in the current source packages, so that would<br>
be a better fit.<br>
<br>
Also, one more thing the three of us (Mouaad, Kai-Chung and I)<br>
discussed was having one source package here with provides the 24<br>
platform packages.<br>
So pkg:google-android-platform-installer provides<br>
pkg:google-android-platform-23 and such.<br>
<span class="">><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>
</span><span class="">> _______________________________________________<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>
</span>Another thing which I thought about, which I hinted in my last e-mail,<br>
was mixing and matching components from the binary packages and the<br>
source built packages.<br>
<br>
So perhaps we can have a 'android-sdk-meta2', or something like that,<br>
which puts symlinks in<br>
/usr/lib/android-sdk2<br>
Those symlinks point to binaries in /usr/lib/android-sdk if we have a<br>
working version, /usr/lib/google-android-sdk otherwise (assuming the<br>
newly created google-android-platform-installer packages install to<br>
that path)<br>
That way we can have a full platform building with as many open source<br>
components as possible, of which we do have quite a few working<br>
already. The missing stuff can be used from the binary packages for<br>
the time being. We can use that for aapt, and also for the platform<br>
package above.<br>
<br>
>From what I can tell, the current idea of the platform packages is to<br>
do the same (I might be forgetting things because I'm trying to catch<br>
up on 2 weeks of things at once, apologies if I do), but I also read<br>
the different path suggestion earlier so I think that might be the<br>
best.<br>
<div class="HOEnZb"><div class="h5"><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>