tag 494651 wontfix
stop

On Mon, Aug 11, 2008 at 03:02:10AM -0400, Ariel wrote:
> I'm not sure that this is really wishlist, but anyway:
> 
> dlocate requires locate, but does not work with mlocate.

that's because mlocate is not the same as locate.

> I don't want to install locate because that defeats the entire purpose of
> having mlocate (or slocate) - not allowing uses to find files they can't
> see.
> 
> Is there any way for it to work with mlocate? 

no. this question has been asked before. unfortunately, it's not
possible.

> As far as I know it's fully compatible.

it's not.  it's similar to locate and performs the same job, but in a
different way.

in particular, mlocate does not provide the /usr/lib/locate/frcode
program that locate provides or anything like it.

dlocate requires frcode to generate it's own database. dlocate will not
work without it.  hence dlocate depends on locate.

> And also, does it actually need to have it's own database? Can it use the
> glocal one?

yes, it does, and no it can't. the db generated by locate and mlocate do
not contain information about which package a file belongs to.

> I know I could install locate and then disable it, so just dlocate
> would sue it, but mlocate is a lot faster then slocate or locate, and
> it would be nice to be able to use it's speed for dlocate as well.

see the archived bug reports for dlocate for notes on how to either
disable locate after installing it or import mlocate's db into locate.

http://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;include=subject%3Amlocate;package=dlocate

craig

PS: i'm getting tired of answering this question. i'm going to have to
put it in a README. but i guess people who don't bother to read old bug
reports before submitting a new one aren't likely to read documentation
either. i'll tag this as 'wontfix' rather than close it so it doesn't
get archived.


-- 
craig sanders <[EMAIL PROTECTED]>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to