Migration instructions for 0.7

[locallycompact]

Hi, with the removal of System.PosixCompat.User, what should downstream users be doing who were depending on getUserEntryForName, for example?

[andreasabel]

@locallycompact : If you found an answer to your question, could you please document it here?

[locallycompact]

Solution was to just use https://hackage.haskell.org/package/unix-2.8.1.1/docs/System-Posix-User.html

[locallycompact]

Reopening due to dhall-lang/dhall-haskell#2496 (comment)

[mitchellwrosen]

System.PosixCompat.User was removed because every exposed function either returned dummy data or threw an exception at runtime. I'm not sure why one would ever want that functionality. So, I don't believe there are any users who were depending on a "cross-platform" getUserEntryForName.

Because unix-2.8 changed the shape of a type exposed in that module, the simplest way to maintain unix-compat moving forward was to delete that module entirely.

[mitchellwrosen]

As far as how to fix dhall-haskell: I'm not sure. I'm sorry for the breakage, but I think in some sense it may have been caused in the first place by unix-compat purporting to have a working getUserEntryForName on Windows.

Has anyone on Windows tried using those code paths in dhall-haskell? If they have, would they not eventually come to the dhall-haskell issue tracker with a bug report?