Disable line-ending conversion in repository via .gitattributes

[IllyaMoskvin]

Working on a Windows 7 host currently, I'm getting the following error when provisioning the Vagrant box:

==> default: Running provisioner: shell...
    default: Running: inline script
==> default: stdin: is not a tty
==> default: /tmp/vagrant-shell: ./install.sh: /bin/bash^M: bad interpreter: No such file or directory

Likewise, if I vagrant ssh and run ./install.sh manually...

vagrant@roundware-server:/vagrant$ ./install.sh
-bash: ./install.sh: /bin/bash^M: bad interpreter: No such file or directory

This happens because line-ending normalization is enabled on my machine: the files are being checked out with CR+LF line-endings. Given that most (proper) Windows code editors should handle LF line-endings without CR, we should consider forcing LF line-endings in some manner, or perhaps put a small note in the readme regarding this issue.

Links:

• AskUbuntu - Not able to execute a .sh file: /bin/bash^M: bad interpreter
• StackOverflow - How do I force git to use LF instead of CR+LF under windows?

[13rac1]

Two more options for the readme:

1. I used https://babun.github.io/ while working on win7 on Roundware.
2. Now I'd use the Linux Subsystem for Windows if I had to run Win10 instead of Linux: https://msdn.microsoft.com/en-us/commandline/wsl/install_guide