
Florian Haftmann wrote:
[...] Those configuration packages do not package an existing »foreign« tar ball (towards which rpmbuild seems to be optimized) but are maintained simply in a git repository containing the files according to their place in the file hierarchy. To make rpmbuild work properly, a tar ball has to be generated explicitly first.
Actually I was looking into that just recently and wanted to write about it :-) rpmbuild has a '--build-in-place' option which is exactly what you want I think. With that rpmbuild stays in the current directory and ignores the %setup macro. Ie no extraction of sources that may be specified in the spec file. Other bits you may want to skip (like applying patches) can either be guarded with "%if 0%{!?_build_in_place}" or you pass "--noprep" to rpmbuild which makes it skip %prep entirely. For faster turnaround times during development one can also leverage the --short-circuit and -b* options to jump to specific stages directly. For that purpose it also makes sense to move %configure into %prep actually. So compilation can be executed without the time consuming configure run. Last week the obs-build script also gained support for the build-in-place mode (in git). So rpms for openSUSE packages that already have their spec file alongside the sources in git (all of yast for example) can now be built locally without intermediate tarballs. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Software Solutions Germany GmbH, GF: Ivo Totev HRB 36809 (AG Nürnberg)