[Rpm-maint] [rpm-software-management/rpm] Proof-of-concept native support for vpath-style builds (PR #2886)

[Vít Ondruch]

I am not sure if tying this to the `%setup` is useful, unless there is also some alternative to setup this independently. Maybe if the `%{-s}` also accepted some alternative build name(s).

> A one gotcha here is that special %doc and %license has traditionally worked for both built and pre-existing content.

The files could be gathered in `%{sourcesubdir}` followed by `%{buildsubdir}`, why not. But how often is the documentation build? It never came to my mind that the documentation could be generated during build and I wouldn't mind if only the former was possible. Or actually if neither one worked and the documentation would need to be installed into `%{_buildrootdir}` manually.

BTW this does not update the `make` macros, right? Which are likely more noisy then the `configure` itself. IOW on one `./configure` call, there are typically two make calls, such as `make` and `make install`

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2886#issuecomment-1927267885
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/pull/2886/c1927267885 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20240205/f564204e/attachment.html>