FS#69670 - [plocate] Default /etc/updatedb.conf
Attached to Project:
Community Packages
Opened by Adrian (adrian5) - Wednesday, 17 February 2021, 03:55 GMT
Last edited by Morten Linderud (Foxboron) - Monday, 01 March 2021, 16:48 GMT
Opened by Adrian (adrian5) - Wednesday, 17 February 2021, 03:55 GMT
Last edited by Morten Linderud (Foxboron) - Monday, 01 March 2021, 16:48 GMT
|
Details
The mlocate package ships with an (opinionated)
/etc/updatedb.conf. I liked this, as I didn't have to spend
time researching sane defaults.
Is there a particular reason plocate doesn't do the same? E.g. separation of concerns (not plocate's job) or because having a reduced search space is deemed unnecessary (fast anyway)? If it was an oversight, I'd like to nominate such a file for inclusion. The blacklisted paths in it that I'm familiar with make sense to me, and the resulting plocate.db is 1/3rd smaller on my system. |
This task depends upon
Closed by Morten Linderud (Foxboron)
Monday, 01 March 2021, 16:48 GMT
Reason for closing: Fixed
Additional comments about closing: 1.1.5-1
Monday, 01 March 2021, 16:48 GMT
Reason for closing: Fixed
Additional comments about closing: 1.1.5-1
Comment by
Eli Schwartz (eschwartz) -
Wednesday, 17 February 2021, 04:17 GMT
Comment by
Morten Linderud (Foxboron) -
Wednesday, 17 February 2021, 08:14 GMT
Comment by
Morten Linderud (Foxboron) -
Thursday, 25 February 2021, 17:15 GMT
- Field changed: Status (Unconfirmed → Assigned)
- Task assigned to Morten Linderud (Foxboron)
Does it need to use the same filename? Then it would need to
conflict with mlocate. I'm not sure why it currently renames the
updatedb command name to support installing both, though, is that
useful in practice?
The filename is `/etc/updatedb.plocate.conf`. Upstream is a guy I
know and I have explicitly pointed out the need to separate
command/confs that doesn't conflict with mlocate.
Apparently this was only done for prognm and I can't be bothered
to patch. So renamed updatedb.plocate -> updatedb and adding a
conflicts on mlocate.