Package Management Use-Cases

Making a change to a dependency

We commonly need to make a change in a package that’s not a leaf of the dependency tree, then rebuild all of the packages that depend on it in order to test the change. With MRB, we pull all of the relevant packages into our development area, build, optionally install, and then run.

Stability of Runtime Environment

Due to the stability requirements of running DAQ systems, we must ensure that we get the exact same set of built code for each run of the DAQ during a given time-period. UPS ensures this through its versioning system (adding new versions of dependent products will not change the version of that dependency used during run-time unless specifically activated.)