[Android-tools-devel] Fwd: google-android-platform-* packages WAS: android-platform-libcore/6.0.1+r16-1

[Mouaad Aallam]

Hello,

I've done an example of two packages[1][2] using a shared debconf template
mechanism (which can be applied to other installers).
it works as following:

- First installed package will prompt a frontend asking the using to pick a
mirror (the debconf template name is `google-android-installers`)
- The package will be installed and all future google-android-*-installer
packages will add themselves as users of the template
google-android-installers.
- Removing a package will unregister the package from the template. when
the last package unregisters the template `google-android-installers` is
removed.
- 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.

[1]: https://github.com/Aallam/debian_google-android-platform-23-installer
[2]: https://github.com/Aallam/debian_google-android-platform-24-installer


*Mouaad Aallam*

On Thu, Jul 14, 2016 at 3:31 PM, Chirayu Desai <chirayudesai1 at gmail.com>
wrote:

> Hi,
> As discussed on IRC #debian-mobile
>
> On Tue, Jul 12, 2016 at 11:15 PM, Mouaad Aallam <mouaad at aallam.com> wrote:
> > A start package for Google Android SDK Platform 24[1]
> >
> > [1]:
> https://github.com/Aallam/debian_google-android-platform-24-installer
> 24 is android N, which isn't currently fully available.
> The final SDK is out, which is why we can have the platform package here.
> However the source code is not, and won't be until after the final
> release, which is supposed to be sometime in August / September.
> Also, we won't really be able to test apps made for API 24, as it's
> currently only available in the form of developer preview for a select
> few devices.
>
> 23 is also what we have in the current source packages, so that would
> be a better fit.
>
> Also, one more thing the three of us (Mouaad, Kai-Chung and I)
> discussed was having one source package here with provides the 24
> platform packages.
> So pkg:google-android-platform-installer provides
> pkg:google-android-platform-23 and such.
> >
> > Mouaad Aallam
> >
> > On Mon, Jul 11, 2016 at 4:29 PM, Mouaad Aallam <mouaad at aallam.com>
> wrote:
> >>>
> >>> This approach would make the packaging simpler, but I think we would
> >>> provide a much better experience to users who are installing the
> >>> platforms if there was one Debian package per platform package.  That's
> >>> how the platforms are represented using the `android list sdk` command
> >>> line tool, and the `android` GUI package installer.  That's what
> Android
> >>> devs are used to.
> >>>
> >>> I think it also provides a more Debian-ish experience, I need X so I do
> >>> `apt-get install X`.
> >>
> >>
> >> Alright then, that was just an idea I had :D, let's do it the way you
> just
> >> discribed then.
> >
> >
> >
> > _______________________________________________
> > 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
>
> Another thing which I thought about, which I hinted in my last e-mail,
> was mixing and matching components from the binary packages and the
> source built packages.
>
> So perhaps we can have a 'android-sdk-meta2', or something like that,
> which puts symlinks in
> /usr/lib/android-sdk2
> Those symlinks point to binaries in /usr/lib/android-sdk if we have a
> working version, /usr/lib/google-android-sdk otherwise (assuming the
> newly created google-android-platform-installer packages install to
> that path)
> That way we can have a full platform building with as many open source
> components as possible, of which we do have quite a few working
> already. The missing stuff can be used from the binary packages for
> the time being. We can use that for aapt, and also for the platform
> package above.
>
> From what I can tell, the current idea of the platform packages is to
> do the same (I might be forgetting things because I'm trying to catch
> up on 2 weeks of things at once, apologies if I do), but I also read
> the different path suggestion earlier so I think that might be the
> best.
>
> _______________________________________________
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/android-tools-devel/attachments/20160716/5d2ffcf9/attachment.html>