On Thu, Nov 3, 2011 at 5:56 PM, Joey Hess <j...@kitenet.net> wrote:
> Svend Sorensen wrote:
>> I'm using mr to manage the repositories for the various software that I
>> track. However, I don't want to check out all the repos by default. (The
>> list is getting long). I also don't want to make a modification to the
>> .mrconfig each time I want to check out a repo. (E.g. have 'skip = true'
>> on all repos, and remove the skip if I decide to check out a repo.)
>>
>> I'm looking for a way to do lazy checkouts and updates. A lazy repo
>> would not be checked out unless I run a command to tell mr to check out
>> the repo. (Something like mr checkout foo.) After I force mr to check
>> out a lazy repo, mr would act on the repo for future mr runs.
>>
>> One way to do this is to have skip check for the existence of a
>> different file for each repo. Creating the file would activate the repo.
>> Any ideas for a better approach?
>
> Good idea! In mr git, you can now use skip = lazy to get this behavior.

Very nice!  I was thinking along very similar lines, so I'm delighted
to see this.  I might need something similar for handling the GNU stow
layer I'm working on, too.

On Thu, Nov 3, 2011 at 6:35 PM, Joey Hess <j...@kitenet.net> wrote:
> Joey Hess wrote:
>> Svend Sorensen wrote:
>> > How do I force mr to checkout a lazy repo? 'mr checkout' seems to ignore 
>> > any
>> > arguments, so 'mr checkout repo' skips repos that have 'skip = lazy'. If I
>> > manually create the repo directory, mr thinks the repo is already checked 
>> > out.
>>
>> Yes, this is a use case for mr checkout somehow taking a parameter, or
>> for the stuff that Adam has been talking about to let mr be told which
>> repos to act on.

Yup - I posted a patch to the other thread for this; works fine for me
so let me know what you think!
_______________________________________________
vcs-home mailing list
vcs-home@lists.madduck.net
http://lists.madduck.net/listinfo/vcs-home

Reply via email to