Hi everyone, We are planning to change Mock's default behavior when building packages. Specifically, we intend to unconditionally pass --noclean to rpmbuild during builds. This means Mock will no longer execute the %clean section of spec files (or the implicit rmbuild cleanup phase). So far, Mock has been using --noclean only when `cleanup_on_success=False` (opt-in behavior).
Modern RPM packaging guidelines consider the %clean section obsolete. Mock already manages the chroot and build root cleanups at the top level before and after builds. Running %clean inside the chroot seems redundant, and is hard to cover correctly (especially with the new "delayed %check" feature). More context and the background discussion can be found in PR #1809: https://github.com/rpm-software-management/mock/pull/1809 Request for Feedback: Before we make this change default in an upcoming release, we would like to hear from the community: Do you have any legitimate use cases where executing the %clean section or rmbuild phase inside Mock is still strictly required? Are you aware of any workflows or tooling built on top of Mock that would break if Mock always passes --noclean? If you have any objections, edge cases, or concerns, or process opinions - please let us know. Thanks, Pavel -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
