Richard Hartmann wrote: > When I use a config like this: > > richih@titanium ~/.config/mr/config.d % cat ikiwiki > [work/git/ikiwiki] > checkout = git clone git://git.ikiwiki.info/ > richih@titanium ~/.config/mr/config.d % > > the checkout ends up in ~/work/git/ikiwiki/git.ikiwiki.info .
This tradeoff was made to allow mr checkout to run entirely arbitrary commands. One common example is to check out a git repository and then run git config in it, or switch to a branch other than master; another is to use an if statement to vary between anonymous and authed checkouts depending on locally available credentials. The downside of allowing arbitrary commands is that they cannot be tweaked to avoid foot-shooting. > Another weird side issue is that if I use > > richih@titanium ~/.config/mr/config.d % cat ikiwiki > [work/git/ikiwiki] > checkout = git clone git://git.ikiwiki.info/ foobar > richih@titanium ~/.config/mr/config.d % > > I end up with work/git/foobar so mr is obviously trying to put > everything into the correct parent directory. It runs the checkout command in the appropriate parent directory. -- see shy jo
signature.asc
Description: Digital signature
