martin f krafft wrote:
> also sprach Joey Hess [2014-09-10 02:44 +0200]:
> > > So saying something like chain=pure is really the same, except it
> > > would handle status/log/diff etc. as well, and implicitly. Maybe
> > > there is also a better way to do it, e.g. chain=true and then
> > > somethin
also sprach Joey Hess [2014-09-10 02:44 +0200]:
> > So saying something like chain=pure is really the same, except it
> > would handle status/log/diff etc. as well, and implicitly. Maybe
> > there is also a better way to do it, e.g. chain=true and then
> > something like skip_all_but_checkout=true
martin f krafft wrote:
> So saying something like chain=pure is really the same, except it
> would handle status/log/diff etc. as well, and implicitly. Maybe
> there is also a better way to do it, e.g. chain=true and then
> something like skip_all_but_checkout=true.
skip = ! lazy will work, althou
also sprach Joey Hess [2014-09-09 21:14 +0200]:
> This would mean that if you cloned d-i into /tmp and followed the
> instructions to use mr in that repo, /tmp/.mrconfig would also be read,
> possibly quite unexpectedly.
This is true. Good point.
All I am trying to do is lowering the barrier of
also sprach Joey Hess [2014-09-09 21:10 +0200]:
> You make it sound like it's walking the filesystem tree, but it's not,
> it's messing around in its data structures from the configs it's already
> loaded.
It's actually using dirname($dir) in a while loop, but it uses the
dirname to index into th
also sprach Joey Hess [2014-09-09 21:06 +0200]:
> If ~/.mrconfig does not chain to ~/some/path/.mrconfig,
> then mr is left looking for the first .mrconfig file it
> can find at or under the current directory. So, when run in
> /some/path/subdir/, it finds that .mrconfig, and ~/.mrconfig, but not
martin f krafft wrote:
> The loadconfig() function does something prefixed by a comment:
>
> # copy in defaults from first parent
>
> in which it walks up the tree
You make it sound like it's walking the filesystem tree, but it's not,
it's messing around in its data structures from the configs
martin f krafft wrote:
> So let's say ~/some/path/.mrconfig specifies
>
> [subdir]
> checkout = …
> chain = true
>
> and ~/some/path/subdir/.mrconfig specifies
>
> [another]
> checkout = …
>
> then, with the status quo, running mr in ~/some/path will work on
> two repos, as it should.
martin f krafft wrote:
> I think this is an inconsistency. When run in bottom-up fashion,
> then either ~/.mrconfig should also be ignored, or all parent config
> files need to be included.
>
> If I had a vote, I'd say that all parent config files should be
> included.
This would mean that if you
also sprach martin f krafft [2014-09-09 07:04 +0200]:
> Bottom-up is when ~/.mrconfig does not know about
> ~/subdir/.mrconfig or ~/subdir/another/.mrconfig. If I now run mr
> in ~/subdir/another,
>
> - ~/.mrconfig and ~/subdir/another/.mrconfig *are* being read
> - but ~/subdir/.mr
also sprach martin f krafft [2014-09-09 05:49 +0200]:
> The manpage specifies:
>
> mr is configured by .mrconfig files, which list the
> repositories. It starts by reading the .mrconfig file in your
> home directory, and this can in turn chain load .mrconfig files
> from repositor
also sprach martin f krafft [2014-04-04 10:42 +0200]:
> mr status: /home/madduck/debian/debconf/team/pub-data
> mr status: /home/madduck/debian/debconf/team/pub-data/.
[…]
> I think this could be done in two ways:
>
> 1. Either chain==true repos should only ever be processed for
> "che
Package: myrepos
Version: 1.20140227
Severity: wishlist
Let's say A chains to B, then A has a stanza [B], which usually also
includes a checkout command.
Within B, if . should also be controlled by mr, then it needs
a stanza for [.]. Now, if mr is run in the context of A, the B root
repository ge
13 matches
Mail list logo
