| Summary: | android SDK software development kit | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Kristoffer Grundström <lovaren> |
| Component: | New RPM package request | Assignee: | David GEIGER <geiger.david68210> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Normal | CC: | cjw, djmarian4u, lda.thedevil.dark, lovaren, marja11, olegbosis, rverschelde |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://source.android.com/source/index.html | ||
| Whiteboard: | X | ||
| Source RPM: | android-sdk | CVE: | |
| Status comment: | |||
|
Description
Kristoffer Grundström
2011-04-14 17:25:05 CEST
Kristoffer Grundström
2011-04-14 17:25:27 CEST
CC:
(none) =>
kristoffer.grundstrom1983 Here's the source: http://source.android.com/source/index.html To build the SDK itself we would likely need ARM cross build tools, if we assume that's the default target architecture for people using the SDK. The android sources include prebuilt binaries but we won't use those. For the android eclipse plugin we would need: - eclipse-gef - can be taken from fedora - eclipse-wst, part of WTP - not very easy to build and package CC:
(none) =>
cjw
Marja Van Waes
2011-10-09 16:21:55 CEST
URL:
(none) =>
http://source.android.com/source/index.html (In reply to comment #2) > To build the SDK itself we would likely need ARM cross build tools, if we > assume that's the default target architecture for people using the SDK. The > android sources include prebuilt binaries but we won't use those. > > For the android eclipse plugin we would need: > - eclipse-gef - can be taken from fedora > - eclipse-wst, part of WTP - not very easy to build and package Now we do have eclipse-gef-3.7.0-1.mga2 / eclipse-gef-3.6.2-2.mga1 Source RPM:
(none) =>
android-sdk Just out of curiosity, what's happening with this? (In reply to comment #4) > Just out of curiosity, what's happening with this? Nothing, unless someone is interested in packaging it. We won't ask for someone to do that, because there are still too many Mdv 2010.2 packages that aren't in Mageia, yet. Those packages should be done first. However, a packager who is interested in android-sdk, is free to package it if there are no legal issues
Marja Van Waes
2012-02-17 17:17:22 CET
Whiteboard:
(none) =>
X my website developer is working on Android too, it'd be nice CC:
(none) =>
djmarian4u is it possible to create the package now? CC:
(none) =>
lda.thedevil.dark Reading info on this page: http://source.android.com/source/building.html makes me doubt it is possible to provide correct packages for android SDK. First its sources are of 8.5 GiB in size and I can not imagine such enormous src.rpm package or even a set of several packages. Second it requires Sun/Oracle's JDK 6 which can not be provided due to license restrictions. The only technically possible solution here is to package prebuilt binary version of this SDK, but I guess it would violate some Mageia policies and rules in packaging. And besides you have to agree to Google License Agreement before using this SDK so I'm in doubt if it's legal to redistribute SDK in binary form (it may include some non-opensource components). CC:
(none) =>
olegbosis
Rémi Verschelde
2014-05-01 21:16:36 CEST
CC:
(none) =>
remi Hi, package android-tools-4.4.2_r2 now imported and submitted on Cauldron (mga5). android-tools contains the ADB service. Closing this bug. Regards daviddavid. Status:
NEW =>
RESOLVED There's an archive missing in the SVN. rpmbuild -ba android-tools.spec complains about not finding extras-4.4.2_r2.tar.bz2 & I can't find it on the SVN, but it does exist in the src.rpm for Cauldron. The tar-archive for core is also missing in the SVN so that should be imported as well. Archives are not hosted in svn.mageia.org/svn/packages Kristoffer. You either have to use mgarepo to get everything, or rebuild the source RPM. |