This sounds an awful lot like reinventing the wheel to me.
Why Tito and not Koji/Mock and the existing Red Hat/Fedora build tools? Does Tito support Koji and/or vice versa?
The tool is intended to solve different problems than these, tito was more about answering questions like:
- How do I tag a new release (in cobbler.git, not Fedora CVS), where do I need to bump version numbers, what's going into the changelog, etc. - As a developer, how can I install Cobbler on my system using the latest source. (something I prefer to do with RPMs as I feel it's more controlled to later remove) - How do I actually generate a tarball or source rpm for a particular tagged release? - How do I generate that tarball for this release with a consistent checksum in the future?
So this is more relevant to an upstream project's release process, independent of the specific tools around Fedora. Even mock only comes into play once you've got a source rpm, tito is involved in getting you to that point. (although now that you mention it an option to do the build in mock would be quite useful)
We did however write some code in Tito for integrating with CVS and Koji because we needed it to handle the volume of package builds involved with Spacewalk. This command checks out the module in CVS, imports the latest spec file and patches from git, builds the tarball, uploads it, and submits builds in Koji. This isn't documented yet as I've only run it against Red Hat's internal build system, but it should work fine in Fedora CVS and Koji, just need to test it.
Cheers,
Devan