Is there any interest in a patchset for mr to manage which repos are being handled?
joey at kitenet.net
Mon Dec 12 17:22:04 CET 2011
Adam Spiers wrote:
> Firstly, I built a library of skip functions:
> which lets me write things like:
> skip = default_skipper || missing_exe gpg
I'm with you so far; this is how I use mr, so in a way it's how mr is
designed to be used.
> However, in the upstream mr, this is not fully implemented yet because
> it does not prevent checkouts of lazy repositories:
> To solve this, I knew mr would need a mechanism for referring to a
> single repository, which in turn would require a new namespace for
This still seems a roundabout way to solve that problem.
Why not just:
if [ "$MR_ACTION" = checkout ]; then
if [ "$MR_FORCE" ]; then
echo "skipping checkout of lazy repo (set MR_FORCE=1 to enable)"
elif [ -d "$MR_REPO" ]; then
Then maybe make --force set MR_FORCE, and to enable one you just:
mr --directory somerepo --force checkout
> except that it's more direct, since if you enable 'foo', surely you
> would checkout 'foo' immediately after. Then the only missing piece
> is 'disable'. Personally I don't need this (yet, at least). But if
> you really needed it, the lazy() skipper could easily be extended (or
> a new skipper written) to perform an extra check:
> test -d .mrdisabled
rm -rf seems a good way to disable a lazy repo.
see shy jo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 828 bytes
Desc: Digital signature
More information about the vcs-home