On Jun 20, 2018, at 7:45 PM, bytevolc...@safe-mail.net wrote:
>
> it is the only compile-time flag that
> determines if a setting is hard-coded or if it is obtained from the
> repository config.
I don’t believe that to be an accurate description of the way the build-time
option behaves. Or at least, it is not an accurate description of ./configure
--with-legacy-mv-rm, which is how you normally set that C preprocessor flag.
I believe all this configuration option does is determines whether the run-time
setting mv-rm-files exists. It doesn’t set it by default, and with that option
unset on a repository, you get the old behavior, the one that doesn’t match
POSIX mv/rm semantics.
After configuring Fossil with this option, you must still set this option on
each repository. Fortunately, this is not difficult:
$ fossil all set mv-rm-files 1
I seem to recall that the “all” command didn’t always work with settings with
arguments, but I might have a hash bucket collision going on right now.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
