-
Notifications
You must be signed in to change notification settings - Fork 55
Pain with CRLF/LF - can't we just make it work either way? #119
Comments
The line endings situation is documented here: A possible way is to add linefeed support to SourceLink.Fake #91 so that it can convert files to the same line endings before compilation. A proposed design for adding source indexes to portable pdb files has SourceLink running before the compile, which would make this pain go away #116. I'm really looking forward to F# support for portable pdb files. dotnet/fsharp#718. |
Note we can't use LF for "visualfsharp" because various tests depend on CRLF as the default on Windows: dotnet/fsharp#954 (comment) It's possible that FSharp.Compiler.Service has a similar dependency, I'm not sure. I suppose the files that require CRLF should be listed like that in gitattributes. |
I'm working on v2 right now. It will be dotnet tooling that supports the https://github.com/ctaggart/SourceLink/blob/v1/SourceLink/Commands.fs#L22 |
:) thanks |
SourceLink seems to be failing again for ProjectScaffold https://ci.appveyor.com/project/fsgit/projectscaffold is the |
I responded in the ProjectScaffold issue. I recommend removing SourceLink v1 and upgrading to use SourceLink v2 as described in the quick start. |
Hi Cameron
As mentioned here we have some problems building repos on Windows that use SourceLink,
Basically we want to use "test=auto" in .gitattributes (since it works well). However then Windows copies of repos get files with CRLF and others with LF somewhat at random. Then SourceLink complains that there's a mismatch. I've been tempted to remove the use of SourceLink because of this but luckily I still have one repo where things build clean and SourceLink passes its validation checks.
Anyway, is there some way to make SourceLink be more forgiving here?
Thanks
Don
The text was updated successfully, but these errors were encountered: