@pmatilai We're using it as part of systemd's development workflow these days.
Being able to incrementally build rpms from a locally checked out tree of the
upstream repository allows us to incorporate package building in the
development workflow itself. I can build an image with newly packaged systemd
rpms from the latest upstream sources and boot it in a virtual machine in about
30s thanks to `--build-in-place`. Without `--build-in-place` we'd have to
remove rpm from our development workflow entirely again, which I would hate to
do because we get more useful test coverage by using rpm since our test images
mimick regular distribution installs more compared to us doing `meson install`
and hoping for the best.
It also makes debugging production issues a joy because I can make a source
code change, get new rpms in 30s, install them, get more feedback, and do the
same thing. This would also be a lot harder without `--build-in-place`.
(This does not take away that any proper rpm build intended to be distributed
widely should always be done from pristine sources)
This is just some feedback on how this option makes my life a lot easier, so
I'm hoping it won't get removed at some point because it conflicts with rpm's
design.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3042#issuecomment-2060484948
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/3042/2060484...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
