Thanks James.. Yes We need to use rpm for version checking and upgrading the software on the client machine. We want to make sure that every time the software is upgraded those configuration file with important data are not overwritten... Just to send .rpm file with zipped executable and config files to the client, so the client can install it safely without worrying about clients mistake... Anyway this my may manager's idea ...:) One important question I have is about building the .rpm file.. RPM documents tell me that the command for building is e.g. rpm -ba myfile.spec But my system does not recognise the -b and gives error of Unknown option.. Is the above command is correct to build final rpm file... I tried to build an .rpm file with already written spec file but still I can not build it.. What I am doing wrong..? Again I am very grateful for all your help Cheers Ali ----- Original Message ----- From: "Chris Jones" <cjones@xxxxxxxxxxxx> To: "RPM Package Manager" <rpm-list@xxxxxxxxxx> Sent: Tuesday, March 23, 2004 2:06 AM Subject: Re: Using rpm as installer > > Hello again; > > On Tue, Mar 23, 2004 at 12:32:00AM -0000, AliN wrote: > > Hi James > > > > Thanks for reply... > > So what I need to do is : > > > > 1 - tar (zip) all the executable and config files > > 2 - Copy the zipped file to /usr/src/redhat/SOURCES > > ...well you said this was a binary install, so you can tar/zip or > whatever them if you want. > > > 3 - Write the .SPEC file which contains only > > Header, PREP( which will only contain scripts to unpack the zipped > > file) which I will presume will put it into /usr/src/redhat/BUILD directory > > 4 - Write install scripts in %install section to copy the files into the > > correct directories > > Well, why not just NOT zip them, then you don't have an extra line to write. > I appologize for the double negative. Unless you plan to repackage this > thing over-and-over again, but then you should probably write a spec > file to compile the source for you as well. > > > > > Now is the above process correct? > > And by the way do I need to have the %file section and which files should > > go there.. > All the files that you want installed in your rpm. Don't forget to set > up the permissions/user stuff. > > Again, unless you are really needing this for version checking, or > upgrade possibilities in the future I would just suggest a straight up > tarball and just smash stuff into /usr/local/<blah> > or wherever else your heart desires. > > ...but I can see the need for the above as mentioned by someone else in > the thread. I don't know how much experience you have with a linux/*NIX > based environment, but you may want to re-analyze your need for RPM if > you really aren't going to be building anything. It may not be worth the > time investment to put this all together if you really don't need it. > > I don't want to discourage you because what you are doing sounds quite > straight forward. > > But perhaps I'm trivalizing your requirements. > > If you are really dead set on using rpm, then might I suggest you take a > look at some other .spec files, you'll quickly get the hang of it. > > Good luck, > > -=chris > > > _______________________________________________ > Rpm-list mailing list > Rpm-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/rpm-list > _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
