||06-13-2005 07:07 PM
checkinstall making symlinks in root??
I've started using checkinstall when compiling from source, and I like it lots, but I've noticed something odd. Checkinstall seems to leave dead symlinks in root ( / ) to libraries associated with the programs I'm installing. For example, after I installed some Python wxWidgets library and g-wrap, my root looked like this:
bin/ libgw-wct.so@ libwx_base_xml-2.6.so@ libwx_gtk2_qa-2.6.so@ spare/
boot/ libgw-wct.so.0@ libwx_base_xml-2.6.so.0@ libwx_gtk2_qa-2.6.so.0@ sys/
dev/ libgwrap-glib.so@ libwx_gtk2_adv-2.6.so@ libwx_gtk2_xrc-2.6.so@ tmp/
etc/ libgwrap-glib.so.1@ libwx_gtk2_adv-2.6.so.0@ libwx_gtk2_xrc-2.6.so.0@ usr/
home/ libgwrap-wct.so@ libwx_gtk2_core-2.6.so@ lost+found/ var/
lib/ libgwrap-wct.so.1@ libwx_gtk2_core-2.6.so.0@ mnt/ wx-config@
libgw-glib.so@ libwx_base-2.6.so@ libwx_gtk2_html-2.6.so@ opt/
libgw-glib.so.0@ libwx_base-2.6.so.0@ libwx_gtk2_html-2.6.so.0@ proc/
libgw-standard.so@ libwx_base_net-2.6.so@ libwx_gtk2_media-2.6.so@ root/
libgw-standard.so.0@ libwx_base_net-2.6.so.0@ libwx_gtk2_media-2.6.so.0@ sbin/
Sorry I didn't get an ls -l, I deleted them before I remembered that I wanted to ask about them. I scrolled up for this listing. Anyhow, those .so@ are all dead symlinks (they point to stuff that no longer exists), with the exception of wx-config which was pointing to something valid, which I could see from the color coding on the terminal. This has happened before with all kinds of packages. And since one doesn't often do an ls in root it can be easy to miss. Has this happened to anyone else? I can't find anything in the docs that would describe this as a feature and I don't think it's a misconfiguration. I am using a stock checkinstallrc and installing packages in the default location, which is usually /usr/local.
Anybody have any thoughts, or similar stuff going on in their root?