Upstream software project

rust-signal-hook-tokio

Tokio support for signal-hook

About rust-signal-hook-tokio

Tokio support for signal-hook

This project links 8 native package records across 2 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. Catalog coverage diagram, not an application screenshot.rust-signal-hook-tokio: recorded package coverageFedora 434 recordsFedora 444 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
rust-signal-hook-tokio
Publisher
Not authoritatively mapped
Native package records
8
Operating systems
fedora-43, fedora-44
License expression
Apache-2.0 OR MIT
Source repository
Not reported

Source-reported description

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

Tokio support for signal-hook. This package contains library source intended for building other packages which use the "futures-core-0_3" feature of the "signal-hook-tokio" crate.

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. Source: rust-signal-hook-tokio

  2. Source: rust-signal-hook-tokio

  3. Source: rust-signal-hook-tokio

  4. Source: rust-signal-hook-tokio

Fedora 44

  1. Source: rust-signal-hook-tokio

  2. Source: rust-signal-hook-tokio

  3. Source: rust-signal-hook-tokio

  4. Source: rust-signal-hook-tokio

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.