Reinstate network-bsd

[lukel97]

As well as some packages that depended on it. This is not a complete list though.

Checklist:

• Meaningful commit message, eg add my-cool-package (please not mention build-constraints.yml)

• At least 30 minutes have passed since uploading to Hackage

• On your own machine, in a new directory, you have successfully run the following set of commands (replace $package with the name of the package that is submitted, and $version with the version of the package you want to get into Stackage):

  stack unpack $package-$version  # $version is optional
  stack init --resolver nightly
  stack build --resolver nightly --haddock --test --bench --no-run-benchmarks
  

[lukel97]

cc @ndmitchell

[juhp]

I think you forgot to leave network-bsd added (ie you removed it completely).
(Noting also that Stackage no longer pulls in deps by itself.)

[lukel97]

@juhp thanks, I wasn't sure where the right place to put it was so I just left it out

[lukel97]

@juhp As an aside, do you know what the terminology "grandfathered dependency" means? I haven't been able to find any mention or reference of it elsewhere

[lukel97]

Looks like travis-ci is failing because of two unrelated hackage updates that snuck in today

[juhp]

I think grandfathered means they don't have a owner in Stackage basically.
It would be better to take ownership if possible, since adding such Stackage "orphaned" packages is not really encouraged.

[juhp]

Merged anyway, thanks :)