Workaround for renaming doesn't work on windows

[fdopen]

The workaround for renaming oUnit doesn't work on windows and probably with other filesystems that are case insensitive.

• ounit/Makefile

  Line 54 in d0e06a9

  ocamlfind install oUnit src/lib/oUnit/META -patch-version $(version)

  will install a directory called oUnit

• ounit/Makefile

  Line 55 in d0e06a9

  dune install ounit

  will re-use this directory and overwrite its content, because the directories oUnit and ounit are identic.
• when the package is installed and oUnit is referenced instead of ounit inside a dune file, oUnit can't be found (the name of the library seems to be determined by the dune-package file, not the directory name). ocamlfind doesn't seem to have this problem.

[gildor478]

I need to try this scenario with Windows, to check what can be done.

If I install ounit 2.1.2 and I have the following dune file:

dune:
(test
(name foobar)
(libraries oUnit))

You think the test will fail to build?

[fdopen]

Yes, I've create #9 in order to see, if I can trigger the error with the CI.

[fdopen]

Windows failure: https://ci.appveyor.com/project/gildor478/ounit/builds/27635212#L653
OS X is also affected: https://travis-ci.org/gildor478/ounit/jobs/589049420#L1530

[gildor478]

Thanks a lot. I can now reproduce the problem. Maybe I can just use REVDEPS=re.

I see 2 solutions for now:

1. Use the --metadir to install a file META.oUnit in a different directory with the name oUnit -- but I am unsure if it will work correctly
2. Create a package ounit2 + ounit2-lwt and install the libraries in ounit2, continue to use the "ocamlfind install oUnit" and depends on ounit2. I think this one will solve the problem...

[gildor478]

The commit 53b9d1a should have solved the issue.

I'll do a release soon, let me know if you think there is a problem.