On Thu, 2013-10-24 at 16:07 -0700, Adam Williamson wrote: > There's only a few times a scratch build isn't practical: if you're > doing a set of chained builds, you can't use scratch builds, as you > can't have one scratch build build against another scratch build. In > this case I use mock: copy the mock .cfg file for the release you want Oh, there's also the case where a build is failing and you can't quite figure out why from the logs a scratch build provides. In this case I use mock in 'interactive' mode: you can pass mock a parameter which gives you a shell inside the mock chroot, so you can poke around within the build environment for a build that failed and figure out what's wrong. Doesn't happen often, though. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
