Dropping `cabal-doctest`

[tchoutri]

Hi @cdepillabout ! I would like to start the discussion about dropping cabal-doctest. It is deprecated, was never intended to be a sustainable solution, and poses a risk for downstream projects who depend (transitively or not) on password.

[cdepillabout]

The problem is that cabal-doctest was the only reliable solution for quite a while!

Now I think cabal-docspec is available, but I haven't actually tried it with any of my repos. Although I'd be happy to switch to cabal-docspec (or really anything else) if someone is willing to put in the time for figuring out how to migrate.

There's a similar issue for another one of my projects: cdepillabout/pretty-simple#82

[tchoutri]

I hear you, I'm not criticising the original decision, our doctest tooling is pretty appalling. The problem with cabal-docspec is that it suffers from the same lack of maintenance will, so it may become a liability. The upside is that it doesn't encroach in the code that is sent to the user, as you can simply get the tarball during CI from GitHub and run it. :)

[tchoutri]

@cdepillabout I've opened #53 :)

[cdepillabout]

@tchoutri I was wondering what your personal motivation is for this. Are you trying to cross-compile password?

[tchoutri]

@cdepillabout Nothing of the sort, I just had a chat with phadej about Cabal 3.6 support and he told me what I say here: He's not proving any maintenance anymore (although someone stepped in but for how long?) and that it was never meant to be a viable solution on the long run.