Aaron Konstam wrote: > On Wed, 2007-08-15 at 10:28 -0500, Mikkel L. Ellertson wrote: >> Aaron Konstam wrote: >>> Place the SRPM in /usr/sr/redhat/SRPMS >>> Then run : rpm -i <src rpm> >>> The spec file will show up in: /usr/src/redhat/SPECS >>> >> This will only work if you run it as root. And the SRPM can be in >> any directory. If you have set up your normal user to build RPMs, >> then running it as a normal user will install the files in the >> $HOME/rpmbuild directory tree. >> >> Mikkel > You are no doubt right about not having to put the src rpm, in the SRPMS > directory bit this method is much simpler and much more straight forward > than the others suggested. I consider working with RPMs to be a root > thing so it would never occur to me to try to build rpms as a normal > user. I can't see how they wold ever install correctly. > For many reasons, including security, I would never build an RPM as root. Something as simple as a mistake in setting buildroot, or a makefile that does not follow %prefix correctly when installing, can mess up the build system when you build as root. But when you build as a user, and use buildroot, you get all the files in the proper directories relative to buildroot, and they are packaged correctly. You control the final ownership and permission in the spec file, so they do not have to match what is in the buildroot tree. I would be very surprised if many experienced Linux/UNIX programmers compile programs, or build RPM's as root. It is not a good practice to get into. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
Attachment:
signature.asc
Description: OpenPGP digital signature
