[Rpm-maint] [rpm-software-management/rpm] --build-in-place multiple flaws (Issue #3131)

[Panu Matilainen]

The %mkbuilddir changes in rpm 4.20 is shaking up the tree and strange fruit are falling out, one of then being --build-in-place option from 0265acbde87036df08da16507a8c4c9a9e6c3c64. There's clearly a call for this functionality, but it's not well defined and is at odds with how rpm likes to do things, so there are all sorts of gaps and flaws in there. There are probably several tickets worth of issues in here, this is just a collection of random remarks while still fresh in memory:

- source rpm generation is effectively undefined behavior because it's just not a meaningful operation
- the only way --build-in-place really makes sense is doing vpath builds, but we don't natively support that in rpm (yet)
- the semantics are not at all clear, this is soooooooo different from normal packaging process
- %patch should be disabled with --build-in-place because it's not a pristine source we can return to
- source/patch meaning is questionable in the first place, because it's not what we build there
- build-in-place always requires spec to be aware of the action, should it instead be an option to %setup instead of cli?
- ...

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3131
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/issues/3131 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20240528/19e39c8d/attachment.html>