First Question:
I'm not a fan of keeping unused sources around. But it seems to me that the only way to update an application, when you're using sources, is to uninstall the original and install the update. If I just keep the Makefile for the uninstall target will that uninstall the original?
Alternatively, I've been thinking of keeping the config.status file in the package user's home directory and recompiling the original source from it when I upgrade. Any comments?
Second Question:
I have not discovered a way, when compiling from source, of upgrading in a similar manner to rpm -U. Have I missed something or does anyone know of a hack or work around so that one of the make targets will actually only remove and install changed files--especially config files that I have edited? Or is my only option to make a back-up of that config file and put it in the appropriate directory after I have installed the updated package?
Third Question:
Has anyone tried making rpm's for the BLFS packages with the patches from the book and scripts for applying procedures and recommendations from the package management hint? I didn't set up my system for portability so that the only thing I can do right now is build the packages and test them on my system. In the future, I may have the time to test a portable build of BLFS.
Thanks,
Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
