[Feedback]: Tool Version Control

[kaitj]

Feedback or Suggestion

For all tools, would be nice to have some way of controlling / selecting the version wrapped. We have the container versions, but this only partially addresses any changes the actual version used but not changes to the code base.

Tool/Package Version (Optional)

No response

[nx10]

I think end users will want to be able to do things like

from niwrap import fsl

out1 = fsl.bet("in.nii", version="5.0.0")
out2 = fsl.bet("in.nii", version="6.0.0")

and everything else just magically works for them.

[kaitj]

I think this makes sense and then the latest version is just the default? Assuming there will also be some sort of interaction with the the container runners?

[nx10]

I think this makes sense and then the latest version is just the default?

Yes I think that would be expected.

Assuming there will also be some sort of interaction with the the container runners?

The version of the wrapper implementation would be selected by the wrappers, but container runner would be able to fetch a default image tag for any given version from the metadata. This should be overridable at version granularity.

Before we can do this though we need the new repo structure #252 as well as some kind of deduplication by the compiler.

We may also want to have global state utilities like

niwrap.fsl.use_version("1.2.3")

[kaitj]

Yeah, I think the global state utilities make sense. The new repo structure also makes sense, but is the container information no longer part of it? That is, would each version of the wrapper not also point to the a specific version of the container? I guess thats the part I am trying to wrap my head around.

[nx10]

Yes a container tag for a specific version would likely be in

src/{package}/{version}/version.json

or a different file at that level e.g.:

src/{package}/{version}/container.json