I manage software installation and upgrades on my Red Hat V6.0 box via RPM.
I was in the process of installing StarOffice, when I realized that there was no RPM package for SO on the CD provided (or anywhere else I know of, for that matter).
I can install SO via the ./install, but I have heard this creates problems down the line with future software installs, as RPM is only aware of files and packages that are installed via RPM.
1) Will an rpm -rebuilddb enable RPM to sense sofware (files) not installed via an RPM package, and update it's files portion of it's database, to continue to detect dependancy/conflict problems?
2) If RPM does not have this capability, how are system administrators dealing with this problem?
Current wisdom seems to be:
1) use RPM exclusivly and wait for RPM's to be released for software, or
2) go with manual install all the way (which does not seem to be very efficient in an enterprise environment.).