You have chosen rpm spec files and macros for your implementation.
Neither was designed for multiple builds in a single package, nor was rpm for
that matter.
Instead of complaining about rpm deficiencies and quirks, you might wish to
rethink your approach, look at the inputs of archive/patch
@ascherer pushed 1 commit.
c288ac1 Add %autosetup option -tN.
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
> For example, the common case of a single well formed compresset tarball with
> a patch in a spec file is even simpler than your design:
>
> %prep
> %setup
> %patch
And that can be trivialy declined in
```specfile
%prep
%setup -z 0
%patch0
%setup -z 1
%patch1
%setup -z 2
%patch2
```
(of