When cabal-rpm cannot resolve which package provides a required library file,
it used to simply omit the dependency from the generated output. The new
--strict flag makes the tool fail with an run-time error instead. This is
useful for people who run cabal-rpm in some kind of batch environment (i.e.
using a makefile) and who want to make sure no errors are missed.
juhp
commented
8 years ago
When cabal-rpm cannot resolve which package provides a required library file, it used to simply omit the dependency from the generated output. The new
--strictflag makes the tool fail with an run-time error instead. This is useful for people who run cabal-rpm in some kind of batch environment (i.e. using a makefile) and who want to make sure no errors are missed.Cc: @mimi1vx