If I have a local manifest file, "repo init" technically doesn't need a -u
argument at all, since the manifest identifies the remote URL anyway.
What steps will reproduce the problem?
1. Create a new directory to work in, e.g: mkdir foo; cd foo
2. mkdir -p .repo/manifests
3. cp -p /path/to/my/custom-manifest.xml .repo/manifests/
4. repo init -m custom-manifest.xml
What is the expected output? What do you see instead?
What *should* happen here is that repo should properly init the tree from the
remote identified in custom-manifest.xml. What actually happens is that it
bombs out complaining that there is no -u argument (even though that argument
will be *ignored*, as it's overridden by the local manifest).
Ideally it'd be possible to say simply:
repo init -m /path/to/my/custom-manifest.xml
and repo would itself emplace a copy of the file at
.repo/manifests/custom-manifest.xml and proceed from there.
Original issue reported on code.google.com by ct...@google.com on 19 Feb 2013 at 8:37
Original issue reported on code.google.com by
ct...@google.comon 19 Feb 2013 at 8:37