On Fri, Nov 12, 2021 at 04:41:48AM +0300, Dmitry Alexandrov wrote: >> It sounds pretty harsh to break a feature used by even the default >> configuration. > Iʼm afraid, that Iʼve failed to locate where switches `-n` or `-e` (and > command line options at all) are used in the default setup.
But /etc/updatedb.conf is read by default, uses the same space-separated syntax, and has spaces in its argument in the default configuration. > Well, Iʼm glad, that youʼve asked, as that allows me to highlight a quite > minor, yet another UI/UX problem: since configuration file cannot be > neither overridden (`--config FILE`) nor disabled entirely (`--no-config`), > I actually feel about it like about a missing stair I have to bear in mind. > It other words, it would not be much of an issue if updatedb did not > support config files at all, and all necessary options were specified in a > wrapper script or even directly in systemd-unit / initscript. OK. I am afraid your feelings about how much of an issue it would be are probably not universal, though. >> and then a flag like --add-single-prunepath that does no splitting? > If thatʼs a question, whether long options that do no splitting have to be > named differently, then yes, sure, as they are explicitly plural now. Well, it's not like I would design a system with this splitting if I made one from scratch, but you know, if you go around changing even the smallest of things between mlocate and plocate, there will be angry bug reports complaining of changed behavior. :-) /* Steinar */ -- Homepage: https://www.sesse.net/
