<div dir="ltr">Yes, I agree with the location you suggested, it was just something I temporarily picked for testing and didn't want to change until I had a working package built.<br><br>Trying to get that working as we speak.</div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jun 9, 2016 at 3:30 PM Hans-Christoph Steiner <<a href="mailto:hans@at.or.at">hans@at.or.at</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
That approach is even better than using a link :) But I still think<br>
that framework-res.apk should not go into /usr/lib/android-sdk. It is<br>
not part of the SDK, and I've never seen that file included in a Google<br>
SDK package. It should go somewhere like:<br>
<br>
/usr/share/android-framework-res/framework-res.apk<br>
<br>
.hc<br>
<br>
Chirayu Desai:<br>
> Re-sending e-mail as first attempt got rejected due to URL blacklist.<br>
><br>
> The content / patch at the URL is:<br>
> diff --git a/brut.apktool/apktool-lib/src/main/java/brut/androlib/res/AndrolibResources.java<br>
> b/brut.apktool/apktool-lib/src/main/java/brut/androlib/res/AndrolibResources.java<br>
> index 0175f3420a..00e4a66579 100644<br>
> --- a/brut.apktool/apktool-lib/src/main/java/brut/androlib/res/AndrolibResources.java<br>
> +++ b/brut.apktool/apktool-lib/src/main/java/brut/androlib/res/AndrolibResources.java<br>
> @@ -576,7 +576,7 @@ final public class AndrolibResources {<br>
> }<br>
><br>
> if (id == 1) {<br>
> - try (InputStream in =<br>
> AndrolibResources.class.getResourceAsStream("/brut/androlib/android-framework.jar");<br>
> + try (InputStream in = new<br>
> FileInputStam("/usr/lib/android-sdk/ramework-res.apk");<br>
> OutputStream out = new FileOutputStream(apk)) {<br>
> IOUtils.copy(in, out);<br>
> return apk;<br>
><br>
><br>
> ---------- Forwarded message ----------<br>
> From: Chirayu Desai <<a href="mailto:chirayudesai1@gmail.com" target="_blank">chirayudesai1@gmail.com</a>><br>
> Date: Thu, Jun 9, 2016 at 12:29 AM<br>
> Subject: Re: [Android-tools-devel] Documenting the android build<br>
> process for tools relevant to us.<br>
> To: Hans-Christoph Steiner <<a href="mailto:hans@at.or.at" target="_blank">hans@at.or.at</a>><br>
> Cc: Android tools Maintainer<br>
> <<a href="mailto:android-tools-devel@lists.alioth.debian.org" target="_blank">android-tools-devel@lists.alioth.debian.org</a>>, 殷啟聰<br>
> <<a href="mailto:seamlikok@gmail.com" target="_blank">seamlikok@gmail.com</a>><br>
><br>
><br>
> On Thu, Jun 9, 2016 at 12:17 AM, Hans-Christoph Steiner <<a href="mailto:hans@at.or.at" target="_blank">hans@at.or.at</a>> wrote:<br>
>><br>
>> Since framework-res.apk has to be built anyway, then I think it makes<br>
>> sense to package it. Sorry I was a bit late to catch up on all the<br>
>> details here.<br>
> My existing patch is not on top of master and won't cleanly apply there.<br>
> Currently master has some code which we may not want / change / is<br>
> work in progress, do we want it there? If so, i can update my patch.<br>
> Kai-Chung, what do you think?<br>
>><br>
>> In terms of apktool's path, I think the apktool should Depend: on<br>
>> android-framework-res, then use a symlink to make sure it is in a path<br>
>> where apktool expects it, i.e. debian/links.<br>
> What upstream currently does is include the apk inside apktool.jar as<br>
> 'brut/androlib/android-framework.jar'<br>
> I have that working, and have a better version of the patch that is<br>
> present on my gitlab account locally.<br>
> However, an alternative approach would be to make apktool read<br>
> framework-res.apk directly from /usr.<br>
> I'm trying that right now with <blacklisted URL snipped> (ignore the<br>
> method deletion, I removed it for testing as it was unused, to avoid<br>
> confusion), but it isn't working.<br>
> I'm not seeing the error right now though, so I'll check this again<br>
> first thing tomorrow morning.<br>
>><br>
>> .hc<br>
>><br>
>> Chirayu Desai:<br>
>>> The platform packages naming / location sounds good.<br>
>>><br>
>>> However, a lot of what the platform zip contains is not available in<br>
>>> Debian right now, and won't really be used anytime soon.<br>
>>> Also, it is generated by grabbing a bunch of components which are<br>
>>> built as part of either the standard Android build process or the<br>
>>> Android SDK build process, both of which are complex. So it would be<br>
>>> best to evaluate what we need from it right now and get that building.<br>
>>><br>
>>> As for framework-res.apk, as discussed on IRC, it is already built for<br>
>>> android.jar, so we can have a separate package for it which would be<br>
>>> used by android.jar as well as apktool right now.<br>
>>> I have that working, see:<br>
>>> <a href="https://gitlab.com/cde/debian_android-tools_android-platform-frameworks-base/commit/1ea978033eb92e0c7c14f1ca40c61d84b2a2e7f1" rel="noreferrer" target="_blank">https://gitlab.com/cde/debian_android-tools_android-platform-frameworks-base/commit/1ea978033eb92e0c7c14f1ca40c61d84b2a2e7f1</a><br>
>>><br>
>>> On Wed, Jun 8, 2016 at 4:56 PM, Hans-Christoph Steiner <<a href="mailto:hans@at.or.at" target="_blank">hans@at.or.at</a>> wrote:<br>
>>>><br>
>>>> I don't see framework-res.apk in the official Android SDK at all, I<br>
>>>> think that's an OS filename, not an SDK file. In the SDK, the framework<br>
>>>> res files are bundled into android.jar and/or installed into the subpath<br>
>>>> data/res/.<br>
>>>><br>
>>>> Also, the platforms packages will be arch-independent since they contain<br>
>>>> nothing that is meant to be executable by the machine that they are<br>
>>>> installed on.<br>
>>>><br>
>>>> .hc<br>
>>>><br>
>>>> 殷啟聰:<br>
>>>>> Hi,<br>
>>>>><br>
>>>>> I was also wondering which package should provide the<br>
>>>>> "framework-res.apk". aapt looks good but in fact the APK is unrelated<br>
>>>>> to this program. How about libandroid-23-java which provides the<br>
>>>>> "android.jar"?<br>
>>>>><br>
>>>>> 1. "framework-res.apk" is built during the process of building "android.jar".<br>
>>>>> 2. aapt is arch-dependent package and "framework-res.apk" is<br>
>>>>> arch-independent file, although I don't know if this point actually<br>
>>>>> matters. Probably reduce the burden of <a href="http://buildd.debian.org" rel="noreferrer" target="_blank">buildd.debian.org</a> ?<br>
>>>>><br>
>>>>> Cheers,<br>
>>>>> Kai-Chung Yan<br>
>>>>><br>
>>>>> 2016-06-07 19:24 GMT+08:00 Markus Koschany <<a href="mailto:apo@debian.org" target="_blank">apo@debian.org</a>>:<br>
>>>>>> On 05.06.2016 11:47, Chirayu Desai wrote:<br>
>>>>>>> Hello everyone,<br>
>>>>>>><br>
>>>>>>> This is to serve as a recap of the discussion had on IRC<br>
>>>>>>> (#debian-mobile) on June 2.<br>
>>>>>>> One of the major things discussed was the build process of<br>
>>>>>>> android.jar, we looked at how it is built in the android tree. I feel<br>
>>>>>>> like that could be documented in a place, so I created a wiki page<br>
>>>>>>> [1].<br>
>>>>>><br>
>>>>>> Good idea. I presume shipping framework-res.apk with<br>
>>>>>> src:android-framework-base would be an easy task. The question is which<br>
>>>>>> package should provide the resource files? Maybe aapt? Apktool already<br>
>>>>>> depends on aapt, so that would be like killing two birds with one stone.<br>
>>>>>><br>
>>>>>> Markus<br>
>>>>>><br>
>>>>>><br>
>>>>>> _______________________________________________<br>
>>>>>> Android-tools-devel mailing list<br>
>>>>>> <a href="mailto:Android-tools-devel@lists.alioth.debian.org" target="_blank">Android-tools-devel@lists.alioth.debian.org</a><br>
>>>>>> <a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel</a><br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> Android-tools-devel mailing list<br>
>>>> <a href="mailto:Android-tools-devel@lists.alioth.debian.org" target="_blank">Android-tools-devel@lists.alioth.debian.org</a><br>
>>>> <a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel</a><br>
><br>
> _______________________________________________<br>
> Android-tools-devel mailing list<br>
> <a href="mailto:Android-tools-devel@lists.alioth.debian.org" target="_blank">Android-tools-devel@lists.alioth.debian.org</a><br>
> <a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel</a><br>
><br>
<br>
_______________________________________________<br>
Android-tools-devel mailing list<br>
<a href="mailto:Android-tools-devel@lists.alioth.debian.org" target="_blank">Android-tools-devel@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel</a></blockquote></div>