ping 0.1.0.4 → 0.1.0.5

raw patch · 3 files changed

+7/−9 lines, 3 filesdep ~optparse-applicativedep ~posix-apidep ~primitive

Dependency ranges changed: optparse-applicative, posix-api, primitive, primitive-containers

Files

• CHANGELOG.md +4/−0
• ping.cabal +3/−3
• src/Network/Icmp/Ping.hs +0/−6

@@ -7,6 +7,10 @@  This project adheres to the [Haskell Package Versioning Policy](https://pvp.haskell.org/). +## [0.1.0.4] - 2023-01-03+- Library now builds with `posix-api-0.4.*`. There was a backwards-incompatible+  change in posix-api when socket families switched to using pattern synonyms.  + ## [0.1.0.3] - 2019-07-22 - Library now builds with newer `posix-api-0.3.*` and with   `primitive-0.7.*`.

@@ -1,6 +1,6 @@ cabal-version: 2.2 name: ping-version: 0.1.0.4+version: 0.1.0.5 synopsis: icmp echo requests description:   This library provides functions that have similar behavior as the@@ -54,7 +54,7 @@     , posix-api >= 0.4 && < 0.5     , primitive >= 0.7 && < 0.8     , primitive-addr >= 0.1 && < 0.2-    , primitive-containers >= 0.3.1+    , primitive-containers >= 0.5     , stm >= 2.5     , transformers >= 0.5.5   exposed-modules: Network.Icmp.Ping@@ -83,7 +83,7 @@   build-depends:     , base >= 4.11.1 && <5     , ip >= 1.5-    , optparse-applicative >= 0.14.3.0 && < 0.15+    , optparse-applicative >= 0.14.3     , ping     , primitive-containers >= 0.3.1     , text >= 1.2.3.1

@@ -9,12 +9,6 @@   , IcmpException(..)   ) where --- TODO: Figure out a more graceful way to fail when someone tries--- to ping the broadcast address. Can this be distinguished from the--- error message that we get when the sysctl thing is not set?------ I think this has been solved.- import qualified Network.Icmp.Ping.Single as S import qualified Network.Icmp.Ping.Hosts as H import qualified Network.Icmp.Ping.Multihosts as M