Philip wrote:
I'm still stuck with the loads and loads of apps that I've already installed from rpm. How do I handle those?
Here's a rather painful hack ...
Assuming you still have the build trees with you, create a list of files installed using "make -n install". Use this list to create a spec file. Write the file so that rpm does nothing during the configure and build stages. The only important part is the files section, and somehow it must be able to figure out where the build tree is! Create rpm from the spec file and then do an "rpm -ivh --force"
Anybody got better ideas?
Maybe it is possible to use the rpm development library to write an app that can directly modify the rpm database? It could take a spec file as input and use the info to update the database ... maybe the library has a perl module as well ...
Thank gawd I never install a tarball without creating an rpm first! ;-)
SameerDS.
_________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com