#652 Scratch build default options do not match the most common usage
Closed: Fixed a year ago by onosek. Opened a year ago by oturpe.

At least according to recent discussion in the Fedora devel list,
the most common usage for scratch builds is to test local changes before pushing.
Unfortunately, currently the default behaviour of rpkg 's scratch-build and build --scratch options just prints an error if local changes are detected.
This is not optimal, the defaults should support the most common usage.

In the linked mailing list discussing the following idea came up:
If no local changes are detected, scratch-build could function just as it already does,
but in case there are local changes, instead of printing an error,
an srpm could be generated and uploaded, as if --srpm option was used.
This would not break any existing non-error usage.


Metadata Update from @onosek:
- Issue set to the milestone: 1.66

a year ago

Login to comment on this ticket.

Metadata
Related Pull Requests
  • #653 Merged a year ago