Allow manifest overlays/superclasses

[GoogleCodeExporter]

Reported by Brian Swetland <swetland@android.com> on Mon Feb 09 10:21:23 PST 
2009
Source: JIRA REPO-3

Quick fix:
- allow local_manifest.xml to indicate items to exclude from the main
manifest.xml

Best fix:
- allow a manifest.xml to specify that it's based on (or a subclass of, etc)
another manifest
- allow a manifest.xml to specify items to exclude from the manifests it
extends

Original issue reported on code.google.com by code-rev...@gtempaccount.com on 24 Sep 2009 at 9:09

[GoogleCodeExporter]

Comment by Shawn Pearce <sop@google.com> on Mon Feb 09 10:22:11 PST 2009

The quick fix was implemented by http://review.source.android.com/4046 and was
in repo 1.4.

The described "best fix" hasn't been started.

Original comment by code-rev...@gtempaccount.com on 24 Sep 2009 at 9:10

[GoogleCodeExporter]

Comment by Shawn Pearce <sop@google.com> on Fri Mar 27 10:18:32 PDT 2009

This could be done with multiple -u options to repo init maybe, resolving the
manifests in the order supplied on the command line.

Original comment by code-rev...@gtempaccount.com on 24 Sep 2009 at 9:10

[GoogleCodeExporter]

Comment by Shawn Pearce <sop@google.com> on Fri Mar 27 10:59:00 PDT 2009

An important consideration here is to make different permutations of manifests
easier, e.g. include the core Android manifest, 3 different chipset manifests,
and a custom device application manifest.  During early device development
many different permutations of chipset manifests might be tested, making for a
lot of permutations of the bottom level child manifest.

Original comment by code-rev...@gtempaccount.com on 24 Sep 2009 at 9:10

[GoogleCodeExporter]

Original comment by sop+code@google.com on 24 Sep 2009 at 11:11