also sprach martin f krafft <madd...@debian.org> [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 repositories. It also automatically looks for a .mrconfig > file in the current directory, or in one of its parent > directories.
After some more debugging on this, I am now fairly certain that the
code does not do this, at least not in "bottom-up" fashion.
Here's what I mean with "bottom-up" vs. "top-down":
Top-down is when ~/.mrconfig chains to ~/subdir/.mrconfig, which
might chain to ~/subdir/another/.mrconfig. If I now run mr in
~/subdir/another, ~/subdir/.mrconfig is sourced.
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/.mrconfig is *not* read
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.
--
.''`. martin f. krafft <madduck@d.o> @martinkrafft
: :' : proud Debian developer
`. `'` http://people.debian.org/~madduck
`- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
