Prev: Miscellaneous Topics
A built-packages-summary target checks the build logs and creates a file with a list of packages that have been built locally (which might be different from a list of packages present, e.g. downloaded toolchain packages). The file is used later for sodiff analysis.
If no packages has been built, a target fake-built-packages-list can be run to generate a list as if all the packages in the rpm output folder were built locally.
sodiff is a process which looks for new versions of .so files and provides a list of packages that need to be rebuilt due to the change.
To provide a list of packages that need to be rebuilt, simply run sodiff-check target. The target will fail if no packages has been built. In that case, one can run fake-built-packages-list target before making a sodiff check. This will allow to analyze all RPMs except just the locally built ones.
The artifacts are available in the $(SODIFF_OUTPUT_FOLDER), which is build/sodiff by default.
The results of sodiff check are:
- summary.txt file, containing a list of source rpm names (without the extension part) of packages that need to be rebuilt due to .so version change,
- sodiff.log file, updated throughout the build with names of packages that are currently processed (use tail -f to track progress of the check).
- Files following a naming format: require_$SOFILE, where $SOFILE is a full name of a .so file with updated version. It contains a list of packages that depend on that file.