On Wed, Jan 27, 2021 at 05:27:12PM +0100, Fabio Valentini wrote: > On Wed, Jan 27, 2021 at 5:24 PM Gwyn Ciesla via devel > <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > > > It's needed for testing builds against versions of packages not yet in mock. I use it almost every day. Losing it would make things like testing solib bumps harder. > > I've done local test builds for soname bumps and similar things lots > of times, and I've never used (or thought about using) fedpkg local > for that. > I used "mock --chain" or a combination of "mock --postinstall > --no-clean" for those builds ... which is much closer to what koji > will do with your builds, and gives every build the clean environment > it deserves >:-) If you want to closely replicate that koji will do, then no disagreement that use of mock is the right tool (or just a koji scratch-build). That just isn't a requirement much of the time though. For adhoc development and debugging of RPM spec changes/updates, mock gets in the way and slows things down. I could easily do 10-20 "local" runs while getting an complex change working, and then finish off with just one or two mock build or koji scratch-build to validate it in a pristine build root env at the end. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| _______________________________________________ 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
