clime <clime@xxxxxxxxxxxxxxxxx> writes: > On Mon, 4 Jan 2021 at 20:43, Dan Čermák <dan.cermak@xxxxxxxxxxxxxxxxxxx> wrote: >> >> clime <clime@xxxxxxxxxxxxxxxxx> writes: >> >> > ...snip... >> >> > >> >> > $ preproc-rpmspec pkg.spec.rpkg # prints rendered spec to stdout, >> >> > pkg.spec.rpkg is a spec template >> >> >> >> This would be a viable workaround, but a workaround nevertheless. Since >> >> I am not frequently rebuilding Fedora rpms outside of mock, koji & copr, >> >> I cannot tell how much of a show-stopper that is though. At least I >> >> think that the benefits of the change need to be pretty big to outweigh >> >> this potential downside. >> > >> > If I may ask, why do you think using preproc-rpmspec is a workaround? >> >> I consider it a workaround, because it adds another step to the >> packaging process outside of koji & copr: it still works, but you have >> to go through extra steps. > > Yes, there is an extra step that would be wrapped in higher-level tooling. > > But when you said "workaround", I was thinking that you actually saw > the correct solution because "workaround" is imho used usually when > someone can't or don't want to solve things the right way so he/she > takes a shortcut. So I was curious what you think is "the right way" > here. Imho the "right way" would be to integrate this into rpmbuild itself instead of adding another layer on top of it. Cheers, Dan
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
