Upstream software project

rust-scratch

Shared compile-time directory

About rust-scratch

Shared compile-time directory

This project links 4 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: 2 package records; Fedora 44: 2 package records. Catalog coverage diagram, not an application screenshot.rust-scratch: recorded package coverageFedora 432 recordsFedora 442 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

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

Source-reported description

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

Compile-time temporary directory shared by multiple crates and erased by `cargo clean`. This package contains library source intended for building other packages which use the "default" feature of the "scratch" 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-scratch

  2. Package rust-scratch-devel

    43 (Fedora 43) (Unspecified): Shared compile-time directory

    1.0.9-1.fc43: noarch

    Source: rust-scratch

Fedora 44

  1. Source: rust-scratch

  2. Package rust-scratch-devel

    44 (Fedora 44) (Unspecified): Shared compile-time directory

    1.0.9-2.fc44: noarch

    Source: rust-scratch

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.