Unfortunately so, testcase: emerge -v \<nautilus-2.10 abiword; emerge -u nautilus; ldd /usr/bin/AbiWord-2.2 Darkmere ~ # ldd /usr/bin/AbiWord-2.2 linux-gate.so.1 => (0xffffe000) libnautilus.so.2 => not found libeel-2.so.2 => /usr/lib/libeel-2.so.2 (0xb7f45000) abiword seems to link to nautilus private interfaces if it finds nautilus that it can use, which of course causes breakage because nautilus isn't ABI stable and isn't likely to ever be such. Simple rebuild will disable the nautilus linking, however its obnoxious behaviour. Is it worth it to release an abiword version that simply hardcodes the disable flag for nautilus? (remove the -DHAVE_NAUTILUS=1 that configure adds )
Added an overriding define to 2.2.3 that sets HAVE_NAUTILUS=0 which i made x86 stable just now, hope it works as intended. This got fixed in versions >2.2.3 btw.
