martin f krafft wrote: > Make mr try to chdir() to the dirname() of any .mrconfig files it's > supposed to load. If the chdir() is successful, then the filename is > truncated to basename(). If the chdir() is unsuccessful, then processing > happens as before.
This seems to chdir and then not chdir back. How does it avoid breaking existing setups? > There may be parent .mrconfig files between ~/.mrconfig and ./.mrconfig > that is not chain-loaded from ~/.mrconfig. Such is the case if you e.g. > download a team-repository to work (such as the debconf-team repo), but > you don't want to put it into the ~/.mrconfig chain. Is this patch somehow related to the bug report it was sent to? Complicating a bug report is a good way to not get it fixed, and slow down all subsequent attempts to fix it.. The idea of chaining is that you tell mr to go load the mrconfig file from some repository it knows about. That chained repository's .mrconfig file can in turn define another repository, and tell mr to chain-load from it too, thus producing a ~/.mrconfig -> ~/project/.mrconfig -> ~/.project/subproject/.mrconfig chain. This seems to be what you're trying to accomplish in a different way. -- see shy jo
signature.asc
Description: Digital signature
