Yann Dirson wrote: > The "mr bootstrap" functionnality is really useful, but some support > to keep the local version in sync with the URL would be nice. > > The natural idea, since we're dealing with vcs anyway, would be to > have it versionned - much like what google's repo is doing. But since > mr is vcs-agnostic, you would probably want this to be flexible as > well. > > One thought would have to register a "special" repo in .mrconfig, > such that "mr bootstrap" would create .mrconfig as a symlink into that > dir. But that somewhat creates a chicken/egg problem.
You can just put the same .mrconfig that is being bootstrapped into the repository that is checked out at the top level of the bootstrapped tree, and it will be available in the right place for mr -p to use it. I can only imagine this would be insufficient if you can't add the .mrconfig file to the main repository that is being checked out, and for some reason need to keep it in a subsidiary repository. -- see shy jo
signature.asc
Description: Digital signature
