configure.ac: include libnetwork for haiku support

[jessicah]

No description provided.

[jessicah]

Will probably also need backporting.

[andreasabel]

Will probably also need backporting.

@jessicah Thanks for the PR. What should this change be backported to?

[jessicah]

I'm pretty sure I've seen 0.1.2.0 selected by cabal in a couple of instances instead of 2.0.1 whilst building various libraries.

[andreasabel]

I'm pretty sure I've seen 0.1.2.0 selected by cabal in a couple of instances instead of 2.0.1 whilst building various libraries.

NB: 2.0.1 -> 0.2.0.1
Ah I see what you mean. In most cases, older major versions are not maintained, so without special requests we wouldn't do it here either. Users should add lower bound resolv >= 0.2 to their build-depends if they want to utilize this fix, this would be default procedure.

[andreasabel]

@lyokha : Shall we release this as 0.2.0.2? I checked it locally on macOS.
I don't remember: is Windows supported at all? If yes, we should add some CI for it.

[lyokha]

@andreasabel, I would even release this as 0.2.1.0 as adding support for a new OS is a fair new feature. But I have a question to @jessicah. I'm not familiar with Haiku but its docs say that libnetwork is combined from libsocket and libbind. Supposedly, libbind is what really needed for resolv, but it's already checked by configure. So, the question is: do we really need adding libnetwork to configure when we already check libbind?

[jessicah]

@lyokha ah, the wording is a bit weird there. libnetwork is the equivalent of those two libraries on Haiku. Haiku doesn't have libsocket or libbind.

[lyokha]

@jessicah, thank you for clarifying this! @andreasabel, regarding Windows, I don't know if it's supported.

[andreasabel]

I think Haskell PVP would allow a patch release (0.2.0.2) here since the API did not change, we merely fixed a problem.
Or is it that this change could make installation fail where it succeeded before? Then we would need a major bump to 0.3.

[jessicah]

No, I don't believe it would cause a failure from a previous success, as libnetwork would be a) tested last, and b) only succeed if it contained that symbol. And similar patches to configure scripts have been upstreamed for years now ;-)

[lyokha]

I'm not sure what version this should be, 0.2.0.2 seems also good.

[andreasabel]

I tried installation on windows; it fails with configure: error: required <resolv.h> header not found. So I guess we do not have to worry about Windows.

[andreasabel]

Release candidate: https://hackage.haskell.org/package/resolv-0.2.0.2/candidate

[lyokha]

@andreasabel, do not forget to autoreconf - i in the working directory to generate a proper configure before making a dist

[andreasabel]

Ok, published as 0.2.0.2!