mk_sdk_repo_xml.sh doesn't support codename for addon

[todd.lee]

The addon xsd v1 includes the codename element, but it looks as though
the script above does not include it in the list of attrs that it uses
for addons (only api) see below :

<snippet>

# Parse all archives.

ATTRS=(
# for repository packages
Pkg.Revision revision
Pkg.Desc description
Platform.Version version
AndroidVersion.ApiLevel api-level
AndroidVersion.CodeName codename
Platform.MinToolsRev min-tools-rev
Platform.MinPlatformToolsRev min-platform-tools-rev
Extra.Path path
Extra.Vendor vendor
Extra.MinApiLevel min-api-level
Sample.MinApiLevel min-api-level
# for addon packages
vendor vendor
name name
description description
api api-level
version revision
revision revision
)

</snippet>

[Xavier Ducrohet]

The error here is that codename should not be part of the schema.

Codename are used for non final platforms (Honeycomb preview SDK was
shipped with a codename). Since addons are used by OEMs to provide a
custom version of a given platform to represent a given, shipping,
device, there is no reason for them to ship an addon based on a non
final platform.

Xav

> --
> You received this message because you are subscribed to the "Android Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
>

--
Xavier Ducrohet
Android SDK Tech Lead
Google Inc.
http://developer.android.com | http://tools.android.com

Please do not send me questions directly. Thanks!

[todd.lee]

Actually, that use case (OEM shipping Addon based on non-final API) is
particularly useful in our specific situation.
Consider this a +1 for inclusion in both the schema and the xml
generator.

Cheers,
T

> Google Inc.http://developer.android.com|http://tools.android.com

[Xavier Ducrohet]

Can you tell me more about your specific use case?

If you're doing a custom version of Android with custom API that could
be shipped to partners in a non final form, should roll out your
custom version of the SDK Manager that can deal with this.

As it is, we do not want OEMs to ship addon based on non final version
of Android. Supporting it in the SDK Manager is one thing, but the
tools also need to support it (and right now they don't).
We are actually fixing the schema to remove the codename.

Xav