Hello,
> > There are two ways to rectify this situation:
> > 1) Add this field to package called mlocate:
> > Provides: locate
> Adeodato Simó is the maintainer of the mlocate package. I am CCing
> this email to him.
No, I won't add such Provides entry because the "locate" package not
only ships an interface for searching, but some utilities under
/usr/lib/locate which some packages (eg. dlocate) need and mlocate does
not provide.
> One possible solution would be to request the mlocate package
> maintainer to put a conflict on the locate package. If he is not
> willing to do that, then that means a user is free to have both. If a
> user can have both locate, mlocate side-by-side why should texmacs
> deprive him of that privilege?
Such Conflicts entry would not be appropriate either, because that would
prevent users from using mlocate, while having locate installed because
of some package depending on the above mentioned utilities.
By the way, Juhapekka, I think your problem can be addressed by just
rm'ing /etc/cron.daily/locate. That's actually what I do. (You could
also talk to the locate maintainer to see if he'd be willing to disable
by default the locate cronjob, unless enabled from /etc/default/locate,
or to not run if mlocate is installed...)
Cheers,
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
Everything you read in newspapers is absolutely true, except for that
rare story of which you happen to have first-hand knowledge.
-- Erwin Knoll
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
