Jan Klötzke

I think the feature will just be about renaming a dependency: ```yaml depends: - name: foo::bar rename: something-else ``` In this case `BOB_DEP_PATHS` will have a `something-else` entry.

Using variable substitution is a different issue IMHO. Currently ```yaml depends: -"${VAR}" ``` isn't supported either. But it could be possible.

Sure. Such a use case with code generators is not too uncommon. So it's definitely a desirable feature. _Theoretically_ every `checkoutScript` marked as `checkoutDeterministic` would be safe to run but...

I'm not sure if this is a problem that warrants the addition of a new keyword. First of all not the whole joined `checkoutScript` would be executed but only the...

I guess your code generator is somehow variant dependent. That should be avoided. You could inspect the generator dependencies via `bob show --format=diff ...` to see what is causing the...

Then the IDL checkout will somehow be variant dependent from the perspective of Bob. Either consult the audit trail or use `bob show` to find out why exactly they are...

Maybe `git` was a bit misleading in the ticket description. In general one should never patch a real SCM like git. I'm more concerned about "url" SCMs. The idea that...

But isn't the `bob status ...` just honest? I mean, this state of the git repository is not upstream. The `checkoutScript` created a state that cannot be compared against a...

> SOLVED: > So I created a new windows user, with got the necessary pathes to msys/usr/bin and to bob! I think this is somthing that must always be solved...

Maybe both? It should be possible to have a native Bob that uses MSYS to execute bash scripts and Bob could be run directly from MSYS as it is now...