On Thu, Jan 21, 2016 at 3:16 PM, Richard Hipp <d...@sqlite.org> wrote:
> On 1/21/16, Stephan Beal <sgb...@googlemail.com> wrote: > > Hiho, > > > > since this is pending review... > > > > http://www.fossil-scm.org/index.html/info/06fd798bdcb9da50 > > > > FYI: that won't compile properly on some systems because C does not allow > > an empty compilation unit, which is what that amounts to when fuse is > > disabled. > This is easily solved by moving the #ifdef to below the #includes > I tried to merge it yesterday, but it gave problems. In particular I > got "command not found" when I ran "fossil fuse" rather than "not > implemented in this build", which I do not think is an improvement. While I obviously don't have the final say on what gets merged to trunk, I would like to try defend my case. If fossil is compiled without fuse support, nobody should be running the fuse command with it. It also shouldn't show up in the listing of "fossil help". As a fossil user on Windows, I find the "fusefs" option listed in the output of "fossil help" akin to annoying noise. The same way that if fossil is compiled without JSON support than it doesn't even include the "fossil json" command. -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı
_______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
