repo should remove projects no longer in manifest

[GoogleCodeExporter]

Reported by Shawn Pearce <sop@google.com> on Sat Feb 28 10:40:55 PST 2009
Source: JIRA REPO-10

From http://code.google.com/p/android/issues/detail?id=1675

repo should delete source directories of projects that get deleted from the
manifest

Repro:
-start with a master branch synced before cupcake was merged into master
-repo sync to the latest (which includes cupcake, and where a project was
moved around)
-try to build

Observed:
the old location of the project that was moved doesn't get cleared, causing
the build system to include makefiles for both the old and new location,
which creates a conflict and causes the build to fail.

Workaround:
Manually delete the offending directory

Note:
repo probably doesn't need full automation to detect the spurious
directories. The manifest could contain a list of known old project
locations that need to be deleted if they're present.

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

[GoogleCodeExporter]

Update by Shawn Pearce <sop@google.com> on Wed Mar 18 14:34:42 PDT 2009

Assigned to Sriram Raman.

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

[GoogleCodeExporter]

Comment by Shawn Pearce <sop@google.com> on Tue Jun 02 11:09:15 PDT 2009

Fixed by https://review.source.android.com/10155

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

[GoogleCodeExporter]

Update by Shawn Pearce <sop@google.com> on Tue Jun 02 11:09:15 PDT 2009

Assigned to Shawn Pearce.
Fixed in version 1.6.8.

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

• Changed state: Fixed