Currently each app is assumed to have a single version. This creates a problem with maintainability since there is are no checks against the external executable version, so users need to have compatible executable versions but there is no good error handling or easy way to document the app version dependencies.
Desired behavior is that app developers should be able to implement a function that allows for the extraction of the version identifier from the expected executable (e.g., additiveFoam for the additivefoam apps). Based of that version identifier, different app templates or other branching logic can be implemented to handle version inconsistencies.
Currently each app is assumed to have a single version. This creates a problem with maintainability since there is are no checks against the external executable version, so users need to have compatible executable versions but there is no good error handling or easy way to document the app version dependencies.
Desired behavior is that app developers should be able to implement a function that allows for the extraction of the version identifier from the expected executable (e.g.,
additiveFoamfor theadditivefoamapps). Based of that version identifier, different app templates or other branching logic can be implemented to handle version inconsistencies.