[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gwl-devel] Next steps for the GWL
From: |
Kyle Meyer |
Subject: |
Re: [gwl-devel] Next steps for the GWL |
Date: |
Fri, 07 Jun 2019 00:11:21 -0400 |
Ricardo Wurmus <address@hidden> writes:
> Kyle Meyer <address@hidden> writes:
>
>> Ricardo Wurmus <address@hidden> writes:
>>
>>>> One of the things I'd love to do
>>>> with GWL is to make it play well with git-annex, something that would
>>>> almost certainly be too specific for GWL itself.
>>
>> [...]
>>
>>> I wonder what the protocol should look like. Should a workflow
>>> explicitly request a “git annex” file or should it be up to the person
>>> running the workflow, i.e. when “git annex” has been configured to be
>>> the cache backend it would simply look up the declared input/output
>>> files there.
>>
>> The latter is what I had in mind. One benefit I see of leaving it up to
>> the configured backend is that it makes it easier to share a workflow
>> with someone that doesn't have/want the requirements for a particular
>> backend.
>
> I agree, this would be convenient.
> I’m not familiar with git annex. Would you be interested in drafting
> this feature, e.g. by writing a patch or specifying how it should work
> in detail?
Sure, I'll work on putting a patch together so there's something more
concrete to discuss.
- Re: [gwl-devel] Next steps for the GWL, (continued)
Re: [gwl-devel] Next steps for the GWL, Kyle Meyer, 2019/06/05
Re: [gwl-devel] Next steps for the GWL, Kyle Meyer, 2019/06/06
Re: [gwl-devel] Next steps for the GWL, Ricardo Wurmus, 2019/06/06
Re: [gwl-devel] Next steps for the GWL,
Kyle Meyer <=
Re: [gwl-devel] Next steps for the GWL, Ricardo Wurmus, 2019/06/12