[Android-tools-devel] Bug#824930: Bug#824930: Bug#824930: Bug#824930: Bug#824930: apktool: creates directories and an empty 1.apk file in $HOME contain

[Paul Wise]

On Thu, 2016-06-09 at 00:32 +0530, Chirayu Desai wrote:

> This was discussed on IRC, and since we already need to build
> framework-res.apk for android.jar (it is extracted and the contents
> are included as-is in the jar), we can also have a separate package
> for it, which I have ready at:

Excellent, perfect resolution to this issue!

It sounds like the package that will contain android.jar should have
Built-Using set to android-framework-res (= $version) so that the
Debian archive will keep the right version available.

> https://gitlab.com/cde/debian_android-tools_android-platform-frameworks-base/commit/1ea978033eb92e0c7c14f1ca40c61d84b2a2e7f1

Nitpicks:

You don't need dh-exec for android-framework-res.install

The android-framework-res package description needs filling out.

I would have put the contents of debian/framework-res.mk into
debian/rules and debian/clean instead.

> I have a patch locally that makes it use ~/.local/share/apktool, can
> update it / push it as preferred.

If the android-framework-res package is installed (should be in the
apktool Depends), I don't think apktool should create any directories
or files in ~/ until the user manually installs another framework.

I don't know enough about which of ~/.local or ~/.cache should be
preferred but it definitely should use one of them instead of what the
upstream developers have chosen.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/android-tools-devel/attachments/20160609/c149fbc2/attachment.sig>