I've got a situation where I need to build a set of static copies of Android source code of different release versions.
Simply doing an "repo init -b $version; repo sync" will take forever (init requires interaction, and the syncs will be wasteful of my bandwidth across versions). My current setup is to download one base version (say 1.6_r1), copy it to a new folder (android-1.6_r2) and then rerun init and sync (repo init -b android-1.6_r2; repo sync). The sync fails sometimes though, with errors like: ndk/build/platforms/android-3/arch-arm/usr/incl Aborting Syncing work tree: 100% (153/153), done. error: development/: platform/development checkout caf83cb2b0ffde1a4cfb7cb258cbe012e283d9e1 Repo sync returned FAIL on android-2.1_r2.1s I've found some posts with similar errors that indicate this might be caused by repo being out of sync with "changed" files in the filesystem, but I'm wondering if my errors are caused by changing versions under repo's nose. Is this the right way to go about changing repository versions? More generally, is there a time/bandwidth efficient way to turn an android-1.6_r1 repository into an android-1.6_r2? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
