In the (hopefully) attached message, Neil Mitchell suggests some tips
for verifying that System.FilePath is compatible with darcs.  Sounds
like this would be worth doing.

I recommend that we start from the outside in (for example, leave
FileName alone for a while, at least those functions which are used by
Darcs.Patch but maybe attack RepoPath and FilePathUtils first)

Attachments

• unnamed

On Sun, Aug 31, 2008 at 10:48:06PM +0000, Eric Kow wrote:
> In the (hopefully) attached message, Neil Mitchell suggests some tips
> for verifying that System.FilePath is compatible with darcs.  Sounds
> like this would be worth doing.

Per Neil's comments, I got a checkout of the filepath repo.

    darcs get http://darcs.haskell.org/libraries/filepath/

Unfortunately "cabal test" does not work, and test/ only contains a
Windows script to perform testing.  Translating it by hand, I tried

    cd test
    runghc GenTests
    ghci -i.. -cpp -DTESTING FilePath_Test.hs

I get this:

    AutoTest.hs:8:31: Module `Test.QuickCheck' does not export `check'
    Failed, modules loaded: none.

I guess this is because filepath isn't compatible with QuickCheck 2,
and versioned imports are provided at the cabal level and don't have
any effect when you manually use ghci as above.

So: I give up.  Someone else can look into this further.

Too late; we've already started using FilePath and in any case, I don't think
we'll *ever* get around to this.