System.FSNotify does not export type WatchConfig about hfsnotify HOT 9 CLOSED

Stack currently has an fsnotify constraint of < 0.4, are you trying to update Stack to the new version?

Sure, I'd be fine with exporting WatchConfig.

from hfsnotify.

6433c5a

from hfsnotify.

@thomasjm, many thanks. I am indeed in the process of making Stack 'fsnotify >= 0.4 ready'. The existing upper bound was added to help people who use Cabal (the tool) to build Stack.

from hfsnotify.

@thomasjm, may I ask another question: in the Cabal file, why do you use executable tests, rather than a test-suite section? (Stack and Cabal (the tool) build executables with the library, but only build test suites on request.)

from hfsnotify.

It's because I like to use the TUI interface of Sandwich to run tests in development, which works better as an executable (codedownio/sandwich#35).

We could backtrack on this if it's causing problems though.

If you're a Stack developer, any chance you'd be the right person to talk to about making stack test able to set up a TTY for the test process? :)

from hfsnotify.

On executable tests, 'problems' is putting it too high, but I think it would be good for users of the fsnotify library to be able to choose not to build the executable (and its dependencies). Would you consider using a Cabal flag?

On Stack, I am more of a janitor than an architect but if you have an idea about how stack test (aka stack build --test) could be extended, please do open an issue in the Stack repository.

from hfsnotify.

Would you consider using a Cabal flag?

It's certainly possible, although I don't enjoy tweaking cabal flags in packages I use. The best solution in general would be to fix this in Stack (and also Cabal). But in the short term, if it's causing pain for hfsnotify users, it's not a big deal to turn it back into a test-suite.

from hfsnotify.

c7e9722

from hfsnotify.

Thanks!

from hfsnotify.