On Tue, Oct 4, 2016 at 10:22 AM, Pierpaolo Bernardi <olopie...@gmail.com>

> On Tue, Oct 4, 2016 at 6:15 PM, Richard Hipp <d...@sqlite.org> wrote:
> > See https://www.fossil-scm.org/aux-test/doc/trunk/aux.md
> >
> > Apparently if a Fossil repository contains a file whose basename is
> > "aux", then an attempt to open or check-out that repo fails with an
> > error.  Only the basename needs to be "aux".  The full name can be
> > things like "src/aux.c" or "doc/aux.txt".
> >
> > Does anybody know of a reasonable work-around?
> According to this page, it looks like it can be done:
> https://blog.onetechnical.com/2006/11/16/forbidden-file-and-
> folder-names-on-windows/
> But in practice these are forbidden names in windows, the only
> reasonable path is to rename these files to something else.

We could modify the Windows code to use the \\.\ prefix trick and then
fossil could create / delete the files. If we did that, how much pain would
it cause to other tools and processes on the Windows system?

If we don't support it, Fossil potentially looks bad to someone for not
creating what appear to be ordinary file names. If we do support it, Fossil
potentially looks bad for creating files or directories that other
processes can't interact with normally.

I wouldn't mind taking a stab at it if enough people think it is
worthwhile, but I'm not sure it is worthwhile.

Scott Robison
fossil-users mailing list

Reply via email to