Indeed, personal habits can break the assumptions behind the design of such apps. What scales fine for some people is a disaster for others.

This laptop has 1.4TB of files in my $HOME, in over six million files. My workstation $HOME has about three times that. I doubt Baloo was intended for such purposes.

Indexing has its place -- I have a Lucy index for my local copy of Wikipedia, for instance -- but I mostly do okay with a categorizing directory structure and stuffing metadata into filenames, like "lq.2013-03-25.topic=4175454453.slackware_on_a_tablet.html" and "howto.slackware.lxc.slackware_ponce_cc_blog_2011_07_17_lxc-containers.html".

So I think that once baloo finally finishes its thing, it will be pretty useful for me, but I'm noticing some other weird behavior. When I first installed -current and Plasma 5 a few days ago, I had a texlive install in my $HOME, which I had forgotten about. Since -current includes texlive now, I got rid of that. Then I stopped baloo, completely removed the index (rm -rf ~/.local/share/baloo), and started it again. Now, with a completely fresh baloo index and no ~/texlive directory, krunner is still returning results from that now-nonexistent directory! How? I have no idea. I can understand removed files persisting for awhile in normal usage, but since I completely removed the index and started over, this doesn't make any sense to me.

There could be some paths defined in the Search settings in the KDE control center. I remember seeing something like that in there when I had Plasma 5.

1 members found this post helpful.

It seems to have eventually purged those on its own. It is slowly but surely indexing file content now. I think it will get there eventually. Here is what it says for the current status:

I still think it needs to be improved with regard to throttling itself down when a user is trying to do other things, especially if it is going to leave a typical system like mine in a nearly-unusable state for hours to days when it first starts up. However, it is a pretty powerful tool once it is finally finished.

1 members found this post helpful.

Also, I stand to be corrected since I haven't run KDE 4 in a LONG time, but doesn't the version that ships with 14.2 also come with baloo? Earlier version but the functionality is meant to be much the same.

IMHO, a nice solution for many users cases is to selectively leave out specific folders when first setting up baloo. For example, i have a "photos" folder, more than 400 GB's and keep growing. Digikam is my helper to find my way there. Having and digikam and baloo searching in there, seems of no great use to me -so i excluded that folder from baloo indexing.

1 members found this post helpful.

I do the same. I shutdown baloo awhile ago, perhaps it's improved. May give it another shot.

Well at this point - I can't help but fan the flames again (The "Is Plasma ready for inclusion in --Current debate-thread) and perhaps it is time that we saw Alien Bob's Plasma in --Current - but right now it is still KDE4 - and if that means including QT5 - then why not at this point? The argument of "well you just want it because it is new and shiny" - that is out the window; as it does not apply here - plus KDE4 was adopted - fairly quickly after their stable release - or maybe could that also be a factor in why there is such a delay in getting Plasma officially, because KDE4 seemed to still be rather buggy(?) - I can't cite that myself as I never used KDE4.


Again though this is just my so take it with the smallest grain of salt anyways - but how much longer is the can going to be kicked down the road - figuratively speaking.... ?

What is the point in asking again? It's unlikely that Pat will answer directly, and he and Eric are already having those discussions. If you want to be helpful, test it and report any issues.

2 members found this post helpful.

I don't expect PV to answer personally, it was more rhetorical anyways; and it is just my views. I feel I also need to point out again that I largely stayed out of the debate anyways (that other thread - Plasma in --Current) - I lurked, but that it I never added my opinion one way or the other. My opinion; again I feel at this point that perhaps it is time to finally take the plunge so-to-speak.

--edit

Plus PV himself wouldn't have to do anything really, as Alien Bob did the work - all he has to do is just replace KDE4 with Alien's packages. Well again he doesn't HAVE to do anything, it is just my opinion anyways.

--edit2

To clarify; PV wouldn't have to do much as Alien has done all the heavy lifting with Plasma, PV would just include Alien's packages; thats all.

I suspect that Mr. Volkerding and Mr. Hameleers are battle testing KDE-plasma on Slackware-current as we speak, and communicating about issues. Mr. Volkerding will remove KDE4 and add KDE5 when it meets his gold standard for excellence. In the 15 years that I've been a Slacker I've admired and appreciated Mr. Volkerding's caution. When KDE5 arrives we'll be good to go.
I can wait.

1 members found this post helpful.

I have no issue with this approach at all - I want the gold standard - however in terms of Plasma; it has been out long enough. Again though perhaps the reasoning for the delay in Slackware - is probably because the issues plaguing KDE4? Again I can't cite that personally as I stopped using KDE(at version 4).


Some will still also interpret this post as impatience, fine; however again given the amount of time Plasma has been out that argument does not apply. Also if PV trusts Alien's packages, thats good enough for me as well its just the waiting and the almost radio silence is what is finally starting to get to me.

2 members found this post helpful.

There's also the possibility that other things are being worked in the background in addition to Plasma5 and Pat wants to make sure they all work when they are pushed out.

He could be working on things like Pam/Kerberos or Wayland and wants to make sure that when things are pushed out, that everything works as expected. Since those can cause fundamental changes in many different aspects of the system, it isn't something as simple as "let's see if plasma5 works"

2 members found this post helpful.

If Mr. Volkerding wants Plasma5 on Wayland, then probably we should kiss goodbye ConsoleKit2 and to hail elogind, at least...

If I remember right, somewhere in this forum Mr. Hameleers told us that Plasma5 needs (at least) elogind for working under Wayland, because ConsoleKit2 is not exactly a complete replacement of systemd-logind.

Hence, I started to wonder if this long delayed adoption of Plasma5 (and probably more other things) isn't in fact a recoil of that vocal presence of "systemd sucks" crowd hanging around there after their beloved Debian infringed their strong opinions based on some Internet myths...

I have no idea if he's even looking at Wayland. We know he was looking at Pam/Kerberos at one point, but I don't remember seeing anything about Wayland. I was just throwing out other ideas he could be playing with internally.

And if he is considering Wayland and needs to switch from ConsoleKit2 to elogind, that just another reason that it could be taking longer to test before he makes the decision to push it out to the public.

1 members found this post helpful.