Simon Pearce
05/10/2025, 7:04 AMSemiBin command, which no longer exists.
From the github:
This will install both the(and now actuallycommand as well (for backwards compatibility), the oldSemiBin2command. For new projects, it is recommended that you exclusively use `SemiBin2`: both commands do the same thing, but `SemiBin2` has a slightly nicer interface.SemiBin
SemiBin has been changed to SemiBin1 in the newest version)
Two things here.
First, I think that the versions string should stay as SemiBin: \$( SemiBin2 --version ), as the developers call it SemiBin in their repository, they have just changed the name of the executable. Like python3 I guess. But I could change it.
Second thing is do we have guidelines for when a tool gets a new module for a separate version?
I think MACS2 and MACS3 are the biggest offenders here personally.
Personally I think that we should only have additional versions of the tool if:
• There is significant changes to the input/output structure
• Enough people need to stick with the previous version of the tool (maybe supports a feature/use-case that is now dropped)
• The tool is important enough to warrant this.
The flip side of this is that the same applies when adding a new tool, we should generally be wary of adding any tool with a number at the end 😉James Fellows Yates
05/10/2025, 7:12 AMJames Fellows Yates
05/10/2025, 7:14 AMJames Fellows Yates
05/10/2025, 7:21 AM