On Oct 4, 2016, at 2:52 PM, Ross Berteig <r...@cheshireeng.com> wrote: > > On 10/4/2016 12:40 PM, Andy Bradford wrote: >> Thus said Richard Hipp on Tue, 04 Oct 2016 12:15:58 -0400: >>> Does anybody know of a reasonable work-around? >> What do other VCS do? > > IMHO, using namespace tricks to create the files or folders with reserved > names will only result in additional mysterious failures and pain for Windows > users. No build systems or compilers will be using those tricks, and even > deleting the files later becomes a problem for the user.
Agreed. If your repository has such file names in it, working around the Windows limitation in Fossil just boots the problem a few squares down the sidewalk, where it will be stumbled upon shortly by some other tool. That said, if y’all decide to support AUX and such on Windows anyway, I wrote some code to do this recently, just to prove a point on unix.stackexchange.com. :) http://pastebin.com/rTs88KmD The code is written for the NUL case, but it’s the same for AUX, CON, etc. If someone wants to use that as a basis for a Fossil patch, the code is currently licensed under cc-by-sa 3.0. That may be liberal enough to include it in Fossil as-is. _______________________________________________ fossil-users mailing list firstname.lastname@example.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users