Use this command line to init a mirror (notice the different manifest URI):
"repo init --mirror -u https://android.googlesource.com/mirror/manifest"
Thanks to the way the manifests are now written, the mirror is
immediately fully functional. Once you've synced a mirror, you can
initialize regular clients from it, via the local filesystem, or ssh,
or a git server if you have that running:
"repo init -u <path_to_mirror>/platform/manifest.git -b gingerbread"
Hopefully people will find this useful.
If you see that some projects seem to be missing from the mirror,
please let me know, I've tried hard to catch them all but it's
possible that I forgot something.
As a note, once you've initialized a client from a mirror, you can
then make it point to the live server by re-running a repo init
command. This is a great way to e.g. store a mirror on a portable hard
drive or on a DVD, use it to initialize multiple machines, and then
have those machines sync future changes from the AOSP server instead.
This is how things could look like overall:
mkdir /usr/local/android-mirror
cd /usr/local/android-mirror
repo init --mirror -u https://android.googlesource.com/mirror/manifest
repo sync
mkdir /usr/local/android-2.3.7
cd /usr/local/android-2.3.7
repo init -u /usr/local/mirror/platform/manifest.git -b android-2.3.7_r1
repo sync
repo init -u https://android.googlesource.com/platform/manifest
repo sync
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
I've added a special manifest that lists all the projects currently in
AOSP (or at least all the ones I currently know about).
Use this command line to init a mirror (notice the different manifest URI):
"repo init --mirror -u https://android.googlesource.com/mirror/manifest"
I just created a master branch in that project, so that one should be
fixed. It's very possible however that I'll have forgotten to create
master branches in other projects, possibly in all the projects that
were used in eclair but not in later releases. I'll try to spot those,
and if you find some on your side, please let me know.
JBQ
> --
> 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
Eventually, though, we'll end up with some projects in there that
don't have master branches (e.g. the kernel sources), so you might
also want to investigate what it'd take for your script to be able to
handle that case as well.
Thanks,
JBQ
I just fixed 4 more. There could be more.
Eventually, though, we'll end up with some projects in there that
don't have master branches (e.g. the kernel sources), so you might
also want to investigate what it'd take for your script to be able to
handle that case as well.
I'm investigating with our git gurus.
JBQ
JBQ
What version of git are you using? I can reproduce here with git version 1.7.3.1
JBQ
--