If the clippy package is not available in the build repos, a warning
is emitted and clippy is not recorded as an enabled tool in the scan
properties. But the scan continues without clippy in this case.
The approach is similar to what --gcc-analyze does. This is needed
because clippy is not available for each mock config and we do not
want to configure the set of enabled tools separately for each mock
config.
kdudka
commented
3 months ago
If the
clippypackage is not available in the build repos, a warning is emitted andclippyis not recorded as an enabled tool in the scan properties. But the scan continues withoutclippyin this case.The approach is similar to what
--gcc-analyzedoes. This is needed becauseclippyis not available for each mock config and we do not want to configure the set of enabled tools separately for each mock config.Related: https://issues.redhat.com/browse/OSH-30