<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>I'm CCing the android-tools list.</div><div><br></div><div>I think it makes sense to make a source package per git repo, unless Google is moving around important files between them a lot, like we saw with AndroidConfig.h. All of the android-platform-* source packages are already organized like that. My main concern with this approach is that it might mean a lot of work in the short term.</div><div><br></div><div>Yeah, the git release tags are a nightmare, they are not consistent nor documented much. I think for now, we should just go with our best guess as to what is the right tag, then we can adjust in the future.</div><div><br></div><div>.hc</div><br><div><div>On Jul 5, 2015, at 8:39 AM, Komal Sukhani wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div>Hello Kai-Chung,<br><br></div><div>Those methods are introduced in higher version of libraries. For example, methods like getAbis(), getDensity() of ddmlib v23.1.0 are used.<br><br></div><div>Komal Sukhani<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jul 4, 2015 at 2:45 AM, 殷啟聰 <span dir="ltr"><<a href="mailto:seamlikok@gmail.com" target="_blank">seamlikok@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Hi Komal,</p><p dir="ltr">Perhaps those APIs that reported missing are actually in buildSrc?</p><p dir="ltr">Hi Hans,</p><p dir="ltr">We found that the android-xxx tags does not exist in all repos, for example platform/tools/buildSrc.</p><p dir="ltr">Cheers,<br>
Kai-Chung Yan</p><div class="HOEnZb"><div class="h5">
<br><div class="gmail_quote"><div dir="ltr">2015 年 7 月 4 日 (週六)04:51 <Komal Sukhani> 於 <a href="mailto:komaldsukhani@gmail.com" target="_blank">komaldsukhani@gmail.com</a> 寫道：<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Hello,<br><br></div><div>I hope you are enjoying in California.<br><br></div>This week I have been working on Android plugin for Gradle. The plugin has dependency over some<br>of Java libraries like sdklib, ddmlib etc. These libraries are provided by source package <a href="https://packages.debian.org/source/sid/androidsdk-tools" target="_blank">androidsdk-tools</a><br>but their current version is 22.2 and one used by plugin is 24.2.0. I have tried using existing libraries but<br>Gradle plugin refers to some of methods that were introduced in higher version. So update is must.<br></div><div><br></div>androidsdk-tools package is fetching code from two different repo, <br> - <a href="https://android.googlesource.com/platform/tools/base/" target="_blank">tools/base</a><br> - <a href="https://android.googlesource.com/platform/tools/swt" target="_blank">tools/swt</a><br><br>Kai-Chung and I were thinking instead of updating the package, it would be easier to maintain the package<br>if we create two separate packages for repos tools/base and tools/swt namely android-platform-tools-base<br>and android-platform-tools-build. This will cover all SDK tools and Android-Gradle-Plugin, but there will<br>be two source packages for SDK tools.<br><br></div>What do you suggest?<br><br></div></div><div dir="ltr">Komal Sukhani<br></div></blockquote></div></div></div><span class="HOEnZb"><font color="#888888"><div dir="ltr">-- <br></div><div dir="ltr"><p dir="ltr">殷啟聰 | Kai-Chung Yan<br>
一生只向真理與妻子低頭<br>
Full-time student of Providence University of Taiwan<br>
LinkedIn: <<a href="https://linkedin.com/in/seamlik" target="_blank">https://linkedin.com/in/seamlik</a>><br>
Blog: <<a href="http://seamlik.logdown.com/" target="_blank">seamlik.logdown.com</a>></p>
</div>
</font></span></blockquote></div><br></div>
</blockquote></div><br></body></html>