title: Understanding how rpmbuild works
body: <p>It seems that the RPM logic is quite different from what I know already and I am having some issues understanding the <em>"RPM logic"</em>. For my work, I have to create a documentation on "How-to create a RPM package on Red Hat 5". </p>
  
  <p>I'm used to Debian and it's derivatives (Ubuntu, and so on) and thus to <em>Debian packages</em> (aka. <code>.deb</code> files).</p>
  
  <p>From what I read, it seems that ones need to be <code>root</code> to create a RPM package. While I understand why <code>root</code> could be required to <em>install</em> a package, I still don't understand why elevated privileges should be needed just to <em>create</em> one.</p>
  
  <p>If I try to create a RPM package as a user, changing the <code>buildroot</code> it fails on the <code>%install</code>step because I don't have permission to write files into <code>/usr/bin</code>. Fair enough but... why does it want to copy my files into <code>/usr/bin</code> at this step?! I just want to create the package, not install it!</p>
  
  <p>I'm sure I'm missing something here. Is there anyone who could give me at least a basic understanding of how <code>rpmbuild</code> works and why?</p>