app-pda/synce-kio-rapip-0.10-r1 gets pulled in when I try to compile synce with the kde use flag enabled. The config fails while complaining that it can't find kde-config, which is actually missing on my system as I use KDE 4 so it should look for kde4-config. When spoofing kde-config (by symlinking to kde4-config, which is bound to fail but trying can't hurt) the config fails on the fact that I don't have Qt3 installed. I'll post some emerge output next to demonstrate the error. It looks to me like the ebuild is missing a constraint. Also, synce-0.13 got released, any chance that one supports a KDE4 KIO slave? Reproducible: Always Steps to Reproduce: 1. Remove KDE3 and Qt3 2. Install KDE4.x and QT4.x 3. emerge app-pda/synce-kio-rapip-0.10-r1
End of emerge run when kde-config is spoofed and Qt3 is still missing: <snip> checking for X... libraries /usr/lib64, headers . checking for IceConnectionNumber in -lICE... yes checking for libXext... yes checking for pthread_create in -lpthread... yes checking for extra includes... no checking for extra libs... no checking for libz... -lz checking for libpng... -lpng -lz -lm checking for libjpeg6b... no checking for libjpeg... -ljpeg checking for perl... /usr/bin/perl checking for Qt... configure: error: Qt (>= Qt 3.3 and < 4.0) (headers and libraries) not found. Please check your installation! For more details about this problem, look at the end of config.log.
Output when kde-config is missing as well (it runs into that before checking for Qt3): <snip> checking for X... libraries /usr/lib64, headers . checking for IceConnectionNumber in -lICE... yes checking for libXext... yes checking for pthread_create in -lpthread... yes checking for extra includes... no checking for extra libs... no checking for libz... -lz checking for libpng... -lpng -lz -lm checking for libjpeg6b... no checking for libjpeg... -ljpeg checking for perl... /usr/bin/perl checking for Qt... configure: error: Qt (>= Qt 3.3 and < 4.0) (headers and libraries) not found. Please check your installation! For more details about this problem, look at the end of config.log.
I'd say we should be dropping this then.