Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In my organization, we deploy all our software to our production machines using RPM. Our build process (which is automated) involves checking out the source from version control, tarring that source directory up, then running rpmbuild using that source tarball. rpmbuild only uses that tarball to untar the sources to work on them. So, it seem like the whole taring and untaring business is just an unneeded extra step in the build process. Is there was a way to just specify the source directory in the spec file, avoiding those extra steps?

share|improve this question
up vote 3 down vote accepted

Yes, you can do that. Do not list any Sources. In the %prep section do not use the %setup macro (which untars the source); rather, just check out the source.

Note that you will not be able to build SRPMs if you do this.

share|improve this answer
This does it. I just need to modify the build procedure to check things out to the rpm BUILD directory instead. Thanks! – Eddie Sep 14 '11 at 21:41

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.