Speaker
Description
Manually maintaining configure/RELEASE files and building EPICS support modules in the correct order is an error-prone and tedious task, especially if different versions of different sets of modules are to be kept around in order for old applications to remain buildable.
SUMO was developed as a tool to automate all of this work. A single JSON file with a simple schema is used to specify dependencies and source locations for each version of each support module in use, keeping the end-application in control of the exact set of module versions it wants to use. The tool is highly configurable and can be easily adapted to different work-flows.