I would like to change the way "quilt setup" is implemented.
At the moment, we call rpmbuild and intercept the calls to tar and patch in order to record the location where archives are extracted and the order and options of the patches which apply to them. Then we replay that record to create our own quilt-compatible source tree.
While this works good enough in simple cases, there are two drawbacks:
- We duplicate archive extraction and patch application, which incurs a performance penalty.
- We miss extra commands from the spec file, so the source tree we produce is not exactly what is specified in the spec file.
What I would like to do is keep intercepting calls to patch, but instead of recording them for later use, I'd like to replace them on the fly by quilt import and quilt push. That way rpmbuild will create a quilt-compatible source tree, which we can just copy over to the final location.
There will certainly be a few issue to solve on the way but I can't foresee any blocker. I hope I'm not overseeing a big obvious and unsolvable problem. If we can get there then I expect "quilt setup" to be better and faster.
Looking for mad skills in:
This project is part of:
Hack Week 11
Porting Moolticute App to openSUSE
Generate branches in kernel.git and kernel-source.git trees to match provided kernel PTFs by sleep_walker
Write a new Dracut module which adds support fo...
In https://github.com/SUSE-Cloud/automation/ we...
Create a parser...