Randy McMurchy wrote: > Richard A Downing wrote these words on 03/15/06 11:09 CST: > >> There appear to be at least three kinds of so called KDE applications: >> >> 1) Those that use QT, but don't depend on KDE at all. >> 2) Those that use KDE libs, but don't depend on the whole of KDE to >> operate (and none of the KDE infrastructure gets started when they run) >> 3) True KDE applications that depend on all the KDE infrastructure. >> >> Even when they are called Kthing, I install type 1 apps in /usr. >> Clearly type 3 apps go in $KDE_PREFIX, I would say. The issue is with >> type 2 apps, and I guess I'd go for $KDE_PREFIX. > > Good observation, Richard. Now to figure out where K3b stands. :-) > > I believe it to be a cross between 2 and 3, perhaps leaning to 3 more > than 2. Here is some additional info that may make it easier to make a > decision where to install it. > > randy 16228 1 0 12:01 pts/9 00:00:00 /home/rml/k3b/bin/k3b > randy 16230 1 0 12:01 ? 00:00:00 kdeinit Running... > randy 16233 1 0 12:01 ? 00:00:00 dcopserver [kdeinit] --nosid > --suicide > randy 16235 16230 0 12:01 ? 00:00:00 klauncher [kdeinit] > randy 16237 1 0 12:01 ? 00:00:00 kded [kdeinit] > randy 16287 16230 0 12:01 ? 00:00:00 kio_file [kdeinit] file > /tmp/ksocket-randy/klauncher >
This indicates to me that it wants to be a full KDE (Type 3) app. Even though it doesn't fail to build if KDEBASE is missing doesn't mean that the next version won't. Interesting analysis - thanks. $KDE_PREFIX for me. R. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
