A updated version of the kio_locate ebuild. kio_locate now uses scons to configure and build.
Created attachment 56743 [details] kio-locate-0.4.0.ebuild updated ebuild. kio-locate now uses scons.
I can't get this to work. For example, if I type "locate:kde" into Konqueror I get the response: An error occurred while loading locate:kde: Could not start process Unable to create io-slave: klauncher said: Error loading 'kio_locate'. Rebooting doesn't help. Here's my emerge info: Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r6-yama i686) ================================================================= System uname: 2.6.11-gentoo-r6-yama i686 AMD Athlon(TM) XP 2100+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.2.3-r5,dev-lang/python-2.3.5 [2.3.5 (#1, May 1 2005, 03:19:10)] ccache version 2.3 [enabled] dev-lang/python: 2.2.3-r5, 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r7 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-mcpu=athlon-xp -O3 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-mcpu=athlon-xp -O3 -pipe" DISTDIR="/data2/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache digest distlocks sandbox sfperms strict" GENTOO_MIRRORS="ftp://mirror.internode.on.net/pub/gentoo ftp://mirror.aarnet.edu.au/pub/gentoo ftp://mirror.pacific.net.au/gentoo ftp://planetmirror.com/pub/gentoo http://gentoo.oregonstate.edu/ http://www.ibiblio.org/pub/Linux/distributions/gentoo" LANG="en_AU" LINGUAS="en_GB" MAKEOPTS="-j2" PKGDIR="/data2/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/data2/portage /data2/portage-bmg-main" SYNC="rsync://mirror.internode.on.net/gentoo-portage" USE="3dnow 3dnowext X Xaw3d a52 aac aalib acpi aim alsa apm arts artswrappersuid audiofile avi bash-completion bindist bitmap-fonts bonobo cdda cddb cdio cdparanoia cdr crypt cups curl dbus dga divx4linux dts dvd dvdr dvdread eds emboss encode esd faad fam fbcon ffmpeg firefox flac flash foomaticdb fortran freetype freetype2 gb gd gdbm ggi ggz gif gimpprint glitz gnome gnome-libs gphoto2 gpm gstreamer gtk gtk2 gtkhtml guile hal howl icq imagemagick imlib ipv6 ithreads jabber java javascript jpeg jpeg2k junit kde kdeenablefinal lesstif libcaca libg++ libwww mad maildir matroska mbox mikmod mmx mng mono motif mozilla mozsvg mp3 mpeg msn ncurses network nocd noplugin nptl nptlonly nvidia objprelink offensive ogg oggvorbis ooo-kde opengl oscar oss pam pdflib perl pic png ppds prelink python qt qtmt quicktime readline real rtc samba scanner sdl shadow slang slp smime snmp speex spell sqlite sse ssl stream svg svga tcltk tcpd tex tga theora threads tidy tiff truetype truetype-fonts type1-fonts unicode usb v4l v4l2 vcd videos vorbis win32codecs wmf wxwindows x86 xanim xface xine xml xml2 xmms xosd xprint xscreensaver xv xvid xvmc yahoo zlib linguas_en_GB userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LC_ALL, LDFLAGS
I should add that I never had problems with 0.3.4 or earlier versions.
Sorry, but I can't confirm this behaviour. It's working fine here. But it sounds if kio-locate wasn't installed properly What does 'etcat -f kio-locate say'? For me it's * kde-misc/kio-locate-0.4.0 /usr/kde/3.4/share/doc/HTML/en/kio_locate /usr/kde/3.4/share/locale/de/LC_MESSAGES /usr/kde/3.4/lib/kde3/kio_locate.la /usr/kde/3.4/share/services/locate.protocol /usr/kde/3.4/share/services/searchproviders /usr/kde/3.4/share/services/locater.protocol /usr/kde/3.4/share/services/searchproviders/locate.desktop /usr/kde/3.4/share /usr/kde/3.4/lib/kde3 /usr/kde/3.4/share/doc/HTML /usr/kde/3.4/share/services /usr/kde/3.4/share/locale/de/LC_MESSAGES/kio_locate.mo /usr/kde /usr/kde/3.4/share/doc/HTML/en/kio_locate/screenshot.png /usr/kde/3.4/lib /usr/kde/3.4/lib/kde3/kio_locate.so /usr/kde/3.4/share/doc/HTML/en/kio_locate/index.docbook /usr/kde/3.4/share/locale/fr/LC_MESSAGES /usr/kde/3.4/share/doc /usr/kde/3.4/share/locale /usr/kde/3.4 /usr /usr/kde/3.4/share/locale/fr/LC_MESSAGES/kio_locate.mo /usr/kde/3.4/share/doc/HTML/en/kio_locate/index.cache.bz2 /usr/kde/3.4/share/locale/de /usr/kde/3.4/share/doc/HTML/en /usr/kde/3.4/share/locale/fr
Thanks for your help. My 'etcat -f kio-locate' output matches yours. I have tried uninstalling/installing kio-locate multiple times, with the same results.
Created attachment 58560 [details] ebuild to install to /usr/share/ I think I may have found the problem. For examining the ebuilds from earlier versions of kio-locate, I ascertained that you need to install to /usr/share/ and not `kde-config --prefix` (which resolves to /usr/kde/3.4 on my system). This ebuild installs to the same place as earlier versions and it works on my system.
Just been taking a look at the new ebuild, and /usr/lib/kde3/kio_locate.la contains the line libdir='var/tmp/portage/kio-locate-0.4.0/image//usr/lib/kde3'. This could cause issues, but could be sedded out. Unfortunately this SCons build file doesn't seem to support DESTDIR=${D} which is normally used. I am starting to learn scons, but not totally up to speed just yet. Ideally the SConstruct file/friends (kde.py) would be patched. Anyone else have any opinions on this?
>Anyone else have any opinions on this? Yes. Maybe someone of the interested users would be so nice and ask the author of kio-locate to have a look at kdissert-0.9 and support DESTDIR and libsuffix=64 as well... :)
kio-locate is incapable of making case-insensitive searches (at least on Gentoo). I have posted an explanation and fix at http://forums.gentoo.org/viewtopic-p-2402844.html#2407971
> kio-locate is incapable of making case-insensitive searches (at least on Gentoo) Good catch. This seems a general problem when using slocate instead of locate, please report it to the author.
At the command line, if I want to filter the results of locate I use grep. One important element of this is that the case sensitivity of these two commands are distinctly separate. If I run "locate -i searchterm | grep FilterTerm" and "locate SearchTerm | grep -i filterterm" I will get different results. In kio-locate, the case sensitivity of terms and filters appear to be combined. I would like to be able to type "locate:searchterm /home/user/Directory" into the Konqueror location bar and have a case insensitive search for "searchterm" be made in the "/home/user/Directory" directory. Instead, the capital "D" in the filter turns the entire query into a case-sensitive search, even though "searchterm" is completely in lower case. A workaround would be to convert "/home/user/Directory" into lower-case, but that is hardly intuitive and it would not work if the search term contained any upper-case letters (since that would make the filters case-sensitive as well). The solution, from what I can see, is to make the filters independent of the search term, much in the same way that grep is distinct from locate. I have reported this bug and the previous one to the author.
Created attachment 63577 [details] ebuild for kio-locate 0.4.2-tvo Here's an ebuild for kio-locate 0.4.2-tvo.
Created attachment 63603 [details] kio-locate-0.4.2-r1.ebuild New ebuild for kio-locate-0.4.2tvo0.1 which uses the mini-install of scons you can find inside the tarball. Addtionally it also works with rlocate (see RDEPEND).
*** Bug 105907 has been marked as a duplicate of this bug. ***
Created attachment 68436 [details] ebuild for kio-locate 0.4.2tvo0.2
Created attachment 68496 [details] kio-locate-0.4.3.ebuild ebuild for kio-locate 0.4.3
0.4.3 in cvs
