Bug#687057: ITP: androidsdk-tools -- A subset of the android sdk tools
Hi Stefan, On 1.10.2012 21:13, Stefan Handschuh wrote: There you go: pkg-java/androidsdk-tools.git I set up generation of OSGi metadata for all JARs we are currently building (also packaged one new required by ADT). Package now uses javahelper for building. This helps to avoid repetitive code in d/rules, which is now greatly simplified. New JAR can be added into build by appending its name and source path to d/javabuild. Javahelper also removes all temporary build files, so no need for clean:: target. All JARs now have Class-Path entry in their manifests, as required by Debian policy. If the package is useful for you in its current shape and you manage to find a sponsor, feel free to let it uploaded. For subsequent versions, I will be adding more libraries as my ADT packaging progresses further (no ITP yet, but I plan to create it soon). Regards, Jakub -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687057: ITP: androidsdk-tools -- A subset of the android sdk tools
Hi Jakub, thanks a lot. I was not sure about how to generate multiple jars with javahelper but thanks to you, I do know that now. Please feel free to also add your name to the copyright of the debian packaging. Currently, I am working on the dalvik package (starting with the dx.jar which is also a requirement for building android packages). There is also some work in progress for aidl, aapt and zipalign. Maybe we should somehow coordinate all efforts in order to act efficiently. Best regards, Stefan Am Donnerstag, den 04.10.2012, 23:29 +0200 schrieb Jakub Adam: Hi Stefan, On 1.10.2012 21:13, Stefan Handschuh wrote: There you go: pkg-java/androidsdk-tools.git I set up generation of OSGi metadata for all JARs we are currently building (also packaged one new required by ADT). Package now uses javahelper for building. This helps to avoid repetitive code in d/rules, which is now greatly simplified. New JAR can be added into build by appending its name and source path to d/javabuild. Javahelper also removes all temporary build files, so no need for clean:: target. All JARs now have Class-Path entry in their manifests, as required by Debian policy. If the package is useful for you in its current shape and you manage to find a sponsor, feel free to let it uploaded. For subsequent versions, I will be adding more libraries as my ADT packaging progresses further (no ITP yet, but I plan to create it soon). Regards, Jakub signature.asc Description: This is a digitally signed message part
Bug#687057: ITP: androidsdk-tools -- A subset of the android sdk tools
There you go: pkg-java/androidsdk-tools.git Best regards, Stefan Am Freitag, den 28.09.2012, 20:30 +0200 schrieb Jakub Adam: Hi Stefan, I looked at your package and see that the java libraries you create will be required by ADT Eclipse plugin once it is packaged. To make those JARs usable in Eclipse, there are some OSGi metadata that must be added to their manifests. In a preparation for ADT packaging (no work have been done yet AFAIK), I'd like to update the manifests. Do you have any source code repository where you store your work? If not, could you please import the package into a git repository of pkg-java team so that others can collaborate? Regards, Jakub signature.asc Description: This is a digitally signed message part
Bug#687057: ITP: androidsdk-tools -- A subset of the android sdk tools
Hi Stefan, I looked at your package and see that the java libraries you create will be required by ADT Eclipse plugin once it is packaged. To make those JARs usable in Eclipse, there are some OSGi metadata that must be added to their manifests. In a preparation for ADT packaging (no work have been done yet AFAIK), I'd like to update the manifests. Do you have any source code repository where you store your work? If not, could you please import the package into a git repository of pkg-java team so that others can collaborate? Regards, Jakub -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687057: ITP: androidsdk-tools -- A subset of the android sdk tools
Hi Jakub, thanks for the interest in this package. I do have a local git repository for the packaging and have just requested access to alioth to upload it directly to the debian packaging repository (pkg-java). As soon as I get access, I will upload the packaging repository such that others can easily contribute. Best regards, Stefan Am Freitag, den 28.09.2012, 20:30 +0200 schrieb Jakub Adam: Hi Stefan, I looked at your package and see that the java libraries you create will be required by ADT Eclipse plugin once it is packaged. To make those JARs usable in Eclipse, there are some OSGi metadata that must be added to their manifests. In a preparation for ADT packaging (no work have been done yet AFAIK), I'd like to update the manifests. Do you have any source code repository where you store your work? If not, could you please import the package into a git repository of pkg-java team so that others can collaborate? Regards, Jakub signature.asc Description: This is a digitally signed message part
Bug#687057: ITP: androidsdk-tools -- A subset of the android sdk tools
Here is the initial package: http://mentors.debian.net/package/androidsdk-tools -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687057: ITP: androidsdk-tools -- A subset of the android sdk tools
@Paul This is a good idea and I posted to #459219 about the plans. @Adrian Not a stupid question at all! This confused me, too. Google has split up the android project into a lot of subprojects (or git repositories). In their platform/sdk subproject for instance zipalign and aapt are missing. Of course, one does not have to keep the project structure that google intended. Am Sonntag, den 09.09.2012, 09:21 +0400 schrieb John Paul Adrian Glaubitz: On Sep 9, 2012, at 3:34 AM, Stefan Handschuh handschuh.ste...@googlemail.com wrote: The sdk tools are containing *some* of the android build tools. Stupid question: Which parts are missing (and what do users miss without them) and why? Cheers, Adrian signature.asc Description: This is a digitally signed message part
Bug#687057: ITP: androidsdk-tools -- A subset of the android sdk tools
Package: wnpp Severity: wishlist Owner: Stefan Handschuh handschuh.ste...@googlemail.com * Package name: androidsdk-tools Version : 14 Upstream Author : The Android Open Source Project * URL : https://android.googlesource.com/platform/sdk * License : Apache 2.0 Programming Lang: Java Description : A subset of the android sdk tools containing the sdklib which is needed to 'compile' android resource files which is a prerequisit to build apk packages. The sdk tools are containing *some* of the android build tools. The sources contain ddms and also the eclipse plugins. However for an initial version, it might be sufficient to create a sdklib binary package that is neede to 'compile' the static android resources of an android application. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687057: ITP: androidsdk-tools -- A subset of the android sdk tools
On Sun, Sep 9, 2012 at 7:34 AM, Stefan Handschuh wrote: * Package name: androidsdk-tools You might want to create a team for packaging Android related things, we already have an android-tools source package containing adb and fastboot: http://packages.qa.debian.org/a/android-tools.html Marcin Juszkiewicz is also planning to package heimdall (the flashing tool). -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687057: ITP: androidsdk-tools -- A subset of the android sdk tools
On Sep 9, 2012, at 3:34 AM, Stefan Handschuh handschuh.ste...@googlemail.com wrote: The sdk tools are containing *some* of the android build tools. Stupid question: Which parts are missing (and what do users miss without them) and why? Cheers, Adrian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
