On Wed, Nov 25, 2009 at 01:03:23PM -0500, Joey Hess wrote: > 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.
Wow, this works just fine - but then maybe some words about this in the doc would be useful: - it is not immediately intuitive that [.] would be a useful construct, or even that it would be accepted by mr. In fact, it is possible that some backends would not allow "checking out into ." and would require some more convoluted checkout line (svn maybe ?) - the 1st repo in the .mrconfig seems to be handled specially (checked out before copying the temporary bootstrap file to .mrconfig), but that does not seem to be mentionned in the manpage. - in fact it is handled so specially that the following bootstrap mrconfig acts as if "chain = true" was specified, which can be somewhat misleading: ==== [.] checkout = git clone <URL> . ==== > 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. Right. Thanks much, -- Yann -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
