I don't work with mock much, but fedpkg is perfectly capable for introducing new things -- that's exactly why I know about/use it.
I draft up specs, build {s,}rpm with fedpkg (indirectly mock), test locally, then ship them off with copr-cli
I draft up specs, build {s,}rpm with fedpkg (indirectly mock), test locally, then ship them off with copr-cli
The doc above (and a former roommate) are the best resources I have!
I've had to expend a bit of trial/error to familiarize myself with a number of quirks... the rough process looks like this:
fedpkg mockbuild
copr-cli build $ProjectName ./results_$PKGNAME/path/to/project.srpm -r $mock_root
This assumes there's an RPM spec file in your working directory and proper handling of sources within/nearby. Fedpkg will create a 'results' directory with the SRPM and RPMsThe -r $mock_root part can be repeated if you want to build against multiple targets in COPR
1) Make spec file
# Gather sources and generate source rpm
2) spectool -gS <specfile>
3) rpkg srpm --outdir .
# The following depends on what I'm trying to do
4a) mock --rebuild -r <chroot> <srpm>
4b) copr build [chroot params] <project> <srpm>
I use fedpkg primarily for dealing with existing packages rather than making my own, where I use rpkg/mock/copr directly.Thank you for sharing, I somehow was completely unaware of rpkg