Adam Spiers wrote: > On Wed, Nov 02, 2011 at 05:02:13PM -0400, Joey Hess wrote: > > Adam Spiers wrote: > > > I notice that chaining to absolute paths does not work, e.g.: > > > Is this a feature or a bug? I would have thought it would be useful > > > to chain to absolute paths. > > > > Probably because nobody noticed since when you're in ~/foo/bar, > > ~/foo/bar/.mrconfig will be read anyway without chaining.
I probably meant to say ~/foo/.mrconfig fwiw.
> I'm beginning to suspect that the way I imagine using mr is
> fundamentally different to everyone else's way. Your previous point
> about mr working best with locality of reference (i.e. each .mrconfig
> being in a parent or near ancestor of the directories containing the
> repos it manages) also contributed to this suspicion. I can
> understand how that makes for clean .mrconfig files with short
> relative paths in the section headers, but I can't understand how you
> could then version control all your .mrconfig files and share them
> across computers. And if you can't, then doesn't that discard a very
> large part of the advantage of using mr in the first place?
>
> I guess it would really help me if one or two people would be kind
> enough to briefly describe the way they use mr, e.g.
>
> - How is your home directory structured, i.e. where do your mrconfig
> files and repos live within it, and which mrconfig files point to
> which repos?
Sure:
~
.mrconfig
doc
.mrconfig
(various document repositories)
src
.mrconfig
(many package sources)
d-i
.mrconfig
lib/backup
.mrconfig (only exists on a few machines, various repositories)
> - How many mrconfig files and mr-managed repos do you have?
190 repos, mostly in src
> - Do you track your mrconfig files with version control?
yes
> - Do you frequently use the -d or -c options?
never
> - Do you usually cd to a particular directory before running mr, and
> if so, why?
I always run mr in the directory I want to affect. Sometimes this
directory contains many repositories, sometimes only one. The point of
mr is I don't need to care how many underlying repositories there are.
If I run it in ~/src/d-i, I want to act on d-i; in
~/src/d-i/package/main-menu I'm only dealing with one package; in ~/src
I want to act on all my source repos.
--
see shy jo
signature.asc
Description: Digital signature
_______________________________________________ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
