[Android-tools-devel] Packages in NEW, copyright files

[Bernhard Reiter]

Am 2014-09-18 um 21:52 schrieb Hans-Christoph Steiner:
> 
> Hey Bernhard,
> 
> Thanks for your note, sorry for the slow response, I was traveling.  

Hi Hans-Christoph,

now it's me who was slow to reply. Sorry, been kinda busy during the
past couple of weeks.

> It is my
> intention to get all of these packages included in jessie, so your help is
> most appreciated.  I just included your patch to
> android-platform-frameworks-native and am in the process of re-uploading.
> 
> About the other fixes you mention, how about you join the android-tools team
> and commit directly?

I sent a membership request via alioth a while ago, but never got any
answer. Also, alioth doesn't allow re-applying. Maybe you can grant me
membership now that Marcin has promoted you to admin? (I'm ockham-guest
on alioth.)

> As for whether this is a complete development environment environment,
> unfortunately there is still quite a bit of work left to do.  My goal was to
> get the tools needed for managing FDroid app repos with the fdroidserver
> package into Debian.  I won't have time to work on getting the rest into
> jessie, but I'm happy to help where I can.

I'm actually an android development noob. Basically, I was thinking that
before trying it out, I wanted to see if I really had to pollute /opt
with some *.deb or tarball downloaded from Google, or if there were any
decent packages already -- or if I could help finishing them.

That said, do you think you could write a page in the Debian wiki on
what components are still missing for a) FDroid and b) "out-of-the-box"
android development using Eclipse (or maybe IDEA, as the SDK seems to be
migrating from Eclipse to that IDE.) ?

> The big one is android-platform-frameworks-base, that one will have to managed
> differently than the others since the git repo is so massive (> 1GB).  

What about git archive and git sparse-checkout? (Not that I've ever used
either of them, but from what I've read, they might be suitable for the
job ...)

> With
> the others, I have made the repos include the upstream git.  That makes it
> really easy to manage making source tarballs since Google does not do that.
> 
> The other big open question is which tags or branches to use?  I have not been
> able to figure out which tags/branches match Google's SDK releases.  There are
> so many overlapping version schemes.

Can't help there either for now, but that question is probably wiki
material, too.

Bernhard

> .hc
> 
> 
> Bernhard Reiter wrote:
>> Hi,
>>
>> I've enthusiastically noticed that the team has produced a couple of
>> packages which are already in the NEW queue.
>> Then again, I've noticed that they've been there for about a month
>> already and wondered why that is?
>>
>> Once those packages are in Debian, will they be sufficient to start
>> Android development (for JB/KK?) right away, or is still anything
>> missing (like an Eclipse plugin)? Are there any docs on how to set up an
>> Android dev environment on Debian using those packages?
>>
>> On another note, I had a quick glance at some of the d/copyright files,
>> and I think the names of the licenses there should be more streamlined
>> with [1], e.g.
>>
>> Apache 2.0 -> Apache-2.0 [or, equivalently, Apache-2]
>> BSD (2 clause) -> BSD-2-clause [same for 3 clause]
>> Todd C. Miller -> ISC [I think]
>>
>> Bernhard
>>
>> [1]
>> https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#license-specification
>>
>> _______________________________________________
>> 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
>>
> 
> _______________________________________________
> 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
>