also sprach martin f krafft <madd...@debian.org> [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 > "checkout", but nothing else, assuming that the sub-repo > specifies [.]; > > 2. One could introduce chain==pure as a keyword to indicate this > condition.
I think there may be a third way:
3. If mr is run in a subdirectory, which is specified in
a parent .mrconfig file, this should be honoured, i.e. the
subdirectory managed according to a parent directory
.mrconfig stanza.
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.
However, running mr in ~/some/path/subdir will only run over
"another", not the repo in the CWD itself, and I don't really see
why it should do that.
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.
So when run in ~/some/path/another, it should read ./.mrconfig, but
it should also read ../.mrconfig (according to the manpage) and
hence process the current directory as well, according to the stanza
in the parent .mrconfig.
Am I overlooking something?
--
.''`. 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)
