Another option, one that wouldn't require actual cleanup logic, would be to
allow the users of `--build-in-place` to obtain a list of paths they could put
into their `.gitignore` file (or their counterparts in other VCS tools). This
could be done by simply RPM defining a macro, or we could add a switch to
`rpmbuild` to print the list on standard output. It could theoretically even
populate the `.gitignore` file automatically.
That said, at that point, we might as well just remove those files like
mentioned in the previous comment, since that would also ensure there's no
interference with subsequent builds...
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/3644#discussioncomment-14711261
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
