Upstream software project

ghc-websockets

A sensible and clean way to write WebSocket-capable servers in Haskell

About ghc-websockets

A sensible and clean way to write WebSocket-capable servers in Haskell

This project links 10 native package records across 3 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Fedora 43: 4 package records; Fedora 44: 4 package records; openSUSE Leap 15.6: 2 package records. Catalog coverage diagram, not an application screenshot.ghc-websockets: recorded package coverageFedora 434 recordsFedora 444 recordsopenSUSE Leap 15.62 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
ghc-websockets
Publisher
Not authoritatively mapped
Native package records
10
Operating systems
fedora-43, fedora-44, opensuse-leap-15-6
License expression
BSD-3-Clause
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

This library allows you to write WebSocket-capable servers. An example server: <https://github.com/jaspervdj/websockets/blob/master/example/server.lhs> An example client: <https://github.com/jaspervdj/websockets/blob/master/example/client.hs> This package only supports insecure ('ws://...') WebSockets. If you need secure ('wss://...') websockets, consider using Wuss: <https://hackage.haskell.org/package/wuss> See also: * The specification of the WebSocket protocol: <http://www.whatwg.org/specs/web-socket-protocol/> * The JavaScript API for dealing with WebSockets: <http://www.w3.org/TR/websockets/>.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. Package ghc-websockets

    43 (Fedora 43) (Unspecified): A sensible and clean way to write WebSocket-capable servers in Haskell

    0.13.0.0-2.fc43: aarch64 x86_64

    Source: ghc-websockets

  2. Package ghc-websockets-devel

    43 (Fedora 43) (Unspecified): Haskell websockets library development files

    0.13.0.0-2.fc43: aarch64 x86_64

    Source: ghc-websockets

  3. Package ghc-websockets-doc

    43 (Fedora 43) (Unspecified): Haskell websockets library documentation

    0.13.0.0-2.fc43: noarch

    Source: ghc-websockets

  4. Package ghc-websockets-prof

    43 (Fedora 43) (Unspecified): Haskell websockets profiling library

    0.13.0.0-2.fc43: aarch64 x86_64

    Source: ghc-websockets

Fedora 44

  1. Package ghc-websockets

    44 (Fedora 44) (Unspecified): A sensible and clean way to write WebSocket-capable servers in Haskell

    0.13.0.0-5.fc44: aarch64 x86_64

    Source: ghc-websockets

  2. Package ghc-websockets-devel

    44 (Fedora 44) (Unspecified): Haskell websockets library development files

    0.13.0.0-5.fc44: aarch64 x86_64

    Source: ghc-websockets

  3. Package ghc-websockets-doc

    44 (Fedora 44) (Unspecified): Haskell websockets library documentation

    0.13.0.0-5.fc44: noarch

    Source: ghc-websockets

  4. Package ghc-websockets-prof

    44 (Fedora 44) (Unspecified): Haskell websockets profiling library

    0.13.0.0-5.fc44: aarch64 x86_64

    Source: ghc-websockets

openSUSE Leap 15.6

  1. Package ghc-websockets

    leap-15.6 (openSUSE Leap 15.6) (Unspecified): A sensible and clean way to write WebSocket-capable servers in Haskell

    0.12.7.3-bp156.3.4: aarch64 ppc64le s390x x86_64

    Source: ghc-websockets

  2. Package ghc-websockets-devel

    leap-15.6 (openSUSE Leap 15.6) (Unspecified): Haskell websockets library development files

    0.12.7.3-bp156.3.4: aarch64 ppc64le s390x x86_64

    Source: ghc-websockets

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.