Christoph Lechleitner wrote:
> Abel Cheung wrote:
>   
>> For those who need command line access, change your habit is the way to go.
>>     
> This ignorance against command line users is annoying, at best!
>
> Matt Zimmerman wrote in that link mailing list message:
>   
>> Today, at least, it doesn't seem to be used, and more featureful indexed
>> searching is provided by tracker, and the overhead of re-indexing daily can
>> be inconvenient for laptop users.
>>     
> Daily reindexing is not necessary!
> For years we used to call updatedb on demand only.
> As of laptop users (and not only them) the system load and power consumation 
> and installation slowdown produced by trackerd and some other stuff (that 
> scans the disc multiple time during installation) is much more disturbing 
> than the simple filename scan of *locate!
>
> Seth wrote:
>   
>> Anyways, I consider this issue well-fixed, and I hope users/dev gap is a 
>> little more bridged on this one :)
>>     
> The issue is not fixed!
> Althought the fix would be very very easy, the hardy package is still broken!
> And hardy as a LTS is supposed to be maintained really well.
>
> Unfortunately it gets more and more clear that Ubuntu's interpretation
> of the term "support" is a joke.
>
>   

No need to shout at another user, mate. That was just my opinion. I was
frustrated by this change just like you. I chose to 'bend' (change of
habit). I still hate it because I am regularly typing mlocate instead of
slocate on my few Feisty boxes left around. I'm sorry to hear that the
slocate package is still in a broken state. I see this thread as an
example how users are welcome to shed their light, tell their
frustrations etc. etc.

I don't think it is realistic to expect every single frustration to be
ironed-out. After all, we all have make priorities. It turns out Ubuntu
didn't share ours in this issue. Bugger. We still let them know. I know
for a fact that that helps Ubuntu devs to be aware of what users need.

Cheers,
Seth

-- 
slocate cron job fails if /etc/updatedb.conf not found
https://bugs.launchpad.net/bugs/189462
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to