Pretty close. The "installation" that occurs as part of the rpmbuild is actually placing the files in a temp location, typically under /usr/var/.... RPMs for installing binaries are the most straightforward since the build step is a no-op. Find an example spec file to modify. That will give you a big leg up the learning curve. Using RPMs for installing software is A Good Thing. What you propose seems pretty sensible. good luck, -tim On 12/29/10 1:42 PM, Clay Stuckey wrote: > I am a little confused regarding what happens in rpmbuild. Here is > what I understand and please correct where I am off: > - when rpmbuild -ba mypackage.spec is executed, the > SOURCE/mypackage.tzg file is ungzipped into BUILD > - the %prep, %build and %install sections of the spec file run > processes on the files in the BUILD directory and actually install the > application to the host filesystem > - the %files section tells rpmbuild which of the recently installed > files to bundle up in to the new RPM > - when the RPM is installed on the new system, it just unpacks those > bundled up files to the new system > Am I understanding this correctly? > > My current needs are to to a few things: > get a few binary files onto a system and excecute to install > alter the contents some config files > alter the permissions of some files and folders > add some users, execute ssh-keygen as them, and place ssh keys in > their authorized_users file > Am I going down the wrong path by considering RPM as a tool for making > these system changes? > > > > > > _______________________________________________ > Rpm-list mailing list > Rpm-list@xxxxxxxxxxxxx > http://lists.rpm.org/mailman/listinfo/rpm-list _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxxxxx http://lists.rpm.org/mailman/listinfo/rpm-list
