Anders Johansson wrote:
On Wednesday 07 December 2005 06:51, B. Stia wrote:
As a slight aside to this question; I recently tried to do an install of an .src and it failed for dependencies. Yet the SOURCES and SPECS for that rpm were found in those respective files. I guess they are useless to me and I could just go in and delete them, no? I also have a ton of files in SOURCES from previous builds. I guess they could be deleted also, right?
Sure. If you don't need them anymore, you can delete them. They are not entered in any database, so you don't have to go through any special procedure to uninstall, rm will do nicely
And, if I do a rebuild of an .src file and it is successful I would find it in the SRPMS directory, right?
No, if you use the -ba (build all) switch with rpmbuild, it will also create a new src.rpm, and if it does, that will be placed in the SRPMS directory. The new binary rpm will be placed somewhere under RPMS (exactly where depends on your architecture)
"rpmbuild -ba" use a spec to control its processing, and uses source files from your SOURCES directory. "rpmbuild --rebuild" operates directly on a src.rpm. Which to use depends on your circumstances: if yoo need to make changes (eg to adapt a Red Hat package to SUSE), then use rpm -i to install it, and rpm -ba to create new binary and src.rpm.s And I have seen dependancy problems when installing a src.rpm. In my case, I found applying a little force was in order.
Have more questions but I am old and confused and it is very late.
:)
Before asking, try some of these things our, and read the rpm documentation. I find I learn better by doing and by trying to do than by asking.