The most common use case for scratch builds is to test local changes before pushing them.
Unfortunately, the defaults options in the scratch-build command did not support this case.
Instead, an error was printed about uncommitted changes.
To support the common case, scratch-build is changed to generate an srpm from local changes when they are detected.
This way, the original behaviour is retained, and additionally the common case can be supported.
The most common use case for scratch builds is to test local changes before pushing them.
Unfortunately, the defaults options in the
scratch-buildcommand did not support this case.Instead, an error was printed about uncommitted changes.
To support the common case,
scratch-buildis changed to generate an srpm from local changes when they are detected.This way, the original behaviour is retained, and additionally the common case can be supported.
This has been discussed in a Fedora devel mailing list thread.
Fixes #652