Bug#824930: [Android-tools-devel] Bug#824930: apktool: creates directories and an empty 1.apk file in $HOME contain
On Thu, 2016-06-09 at 19:31 +0530, Chirayu Desai wrote: > Currently both android.jar and framework-res.apk are built from > android-platform-frameworks-base, and so android.jar uses the current > version directly. Building them both from the same place sounds better. > Why? It didn't work when I tried it without. It doesn't look like you are using any of the special syntax of dh-exec but just normal dh_install syntax. Confusing that it doesn't work, perhaps you need to drop the executable permissions too. > That might need more changes, as currently it will install the system > framework to 1.apk Ok. I don't like cruft but it is a minor issue in the scheme of things. > Yes. The patch I have for this is [3], works well when combined with > [2] (otherwise you get a NPE) Excellent. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#824930: [Android-tools-devel] Bug#824930: apktool: creates directories and an empty 1.apk file in $HOME
On Sat, 2016-05-21 at 17:15 +0200, Markus Koschany wrote: > This is intentional but I must admit I don't like it too. Normally > apktool copies the framework files to this directory or, if it is not > available, to java.io.tmpdir. We probably could change that to > ~/.apktool or ~/.local/share/apktool. Thoughts? I think I would prefer the XDG user cache dir since this isn't really user data but just data cached from elsewhere. > https://ibotpeaches.github.io/Apktool/documentation/#framework-files Thanks for the pointer. > However before you can decode apk files you need to install those > framework files. It would be more convenient for users if those framework files were installed by some Debian package in /usr/share/... -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#824930: [Android-tools-devel] Bug#824930: apktool: creates directories and an empty 1.apk file in $HOME
Am 21.05.2016 um 14:38 schrieb Paul Wise: > Package: apktool > Version: 2.1.1+dfsg-1 > Severity: normal > Usertags: cruft > > For some reason apktool seems to think it is appropriate to create > files in my home directory even though I didn't give permission. [...] This is intentional but I must admit I don't like it too. Normally apktool copies the framework files to this directory or, if it is not available, to java.io.tmpdir. We probably could change that to ~/.apktool or ~/.local/share/apktool. Thoughts? https://ibotpeaches.github.io/Apktool/documentation/#framework-files However before you can decode apk files you need to install those framework files. Question to team members: Are they included in src:android-platform-frameworks-base or can we make them available somehow? The original apktool.jar embeds framework-res.apk from the Android Open Source Project but they are not part of apktool's sources. This bug is also related to https://bugs.debian.org/824933 Markus signature.asc Description: OpenPGP digital signature
