On Sep 29, 2017 7:43 AM, "Andy Goth" <[email protected]> wrote:

On 09/28/17 21:34, Scott Robison wrote:

> There is a winsymlink branch I created some time ago. Hasn't been kept
> up to date (I didn't need it, just thought it might be useful for
> feature parity) but I could take a look at it if you were interested.
> Or you could.
>

I had a peek.  I know Windows NT derivatives allow symlinks to directories
but was not aware any version of Windows allowed symlinks to files.  What
is the status of that?


Vista and later allow symlinks to both, though it treats them as separate
types of symlinks. That is part of the awkwardness of trying to paper over
the differences between posix & Windows.

Having symlinks in Windows may seem cool at first, but it would actually be
counterproductive without a good way to edit them.  If Fossil is the only
program on hand that can create, change, or unlink them, it might as well
not even try.


The system does include utilities to create and delete them.

Plus, the project I'm doing has to work all the way back to Windows 2000
and (maybe, possibly, unconfirmed) Windows 98.


On that my branch cannot help.

  While it's not the end of the world if there are some platforms which
can't be used as a build or development platform, right now I have it so
that any supported system is fully capable of developing for all supported
systems: Linux for Windows, Windows for Linux, etc.  Therefore I do not
want to rely on features that aren't bog standard throughout every version
of Windows, 95 onward because long filenames.


Good luck, though based on my admittedly limited understanding, this seems
like such a departure from what any supported system does that it feels
like a separate utility or make step or something is called for.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to