Yep, this would be just yet another item to add to the checklist in #3131.
That said, this is actually one of the reasons for the introduction of the
guaranteed per-build directory (#2078) in 4.20. Therefore, the semantics of
`--build-in-place` could be (re)defined along the lines of:
1) The caller owns the directory, including any actions necessary to keep it
pristine
2) Any files made by RPM, not just the actual source/binary RPMs, are
considered build artifacts (i.e. including `debugsourcefiles.list` and such)
Then, the caller could implement the cleanup e.g. by using OverlayFS (like you
described in #3131) or using `git clean -fdx` (assuming that the source tree is
a git repo).
Just some random thoughts, @pmatilai might have a better idea as I know he has
spent some time pondering about this :sweat_smile:
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/3644#discussioncomment-12464795
You are receiving this because you are subscribed to this thread.
Message ID:
<rpm-software-management/rpm/repo-discussions/3644/comments/[email protected]>
_______________________________________________
Rpm-maint mailing list
[email protected]
https://lists.rpm.org/mailman/listinfo/rpm-maint
