Upstream software project

cudf

Development files for ocaml-cudf

About cudf

Development files for ocaml-cudf

This project links 7 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

Debian 13 (Trixie): 3 package records; Fedora 43: 2 package records; Fedora 44: 2 package records. Catalog coverage diagram, not an application screenshot.cudf: recorded package coverageDebian 13 (Trixie)3 recordsFedora 432 recordsFedora 442 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
cudf
Publisher
Not authoritatively mapped
Native package records
7
Operating systems
debian-13, fedora-43, fedora-44
License expression
LGPL-3.0-or-later WITH OCaml-LGPL-linking-exception
Source repository
Not reported

Source-reported description

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

CUDF (for Common Upgradeability Description Format) is a format for describing upgrade scenarios in package-based Free and Open Source Software distribution. In every such scenario there exists a package universe (i.e. a set of packages) known to a package manager application, a package status (i.e. the currently installed packages), and a user request (i.e. a wish to change the set of installed packages) that need to be fulfilled. CUDF permits to describe an upgrade scenario in a way that is both distribution-independent and package-manager-independent. CUDF offers a rigorous semantics of dependency solving that enables to independently check the correctness of upgrade solutions proposed by package managers. CUDF adoption would enable to share dependency solver components across different package managers, both intra- and inter-distributions.

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.

Debian 13 (Trixie)

  1. Package cudf-tools

    trixie (Debian 13 (Trixie)) (devel): command line tools for package upgrade problem descriptions

    0.10-6+b1: amd64 arm64

    Source: cudf

  2. Package libcudf-dev

    trixie (Debian 13 (Trixie)) (libdevel): C library to access descriptions of package upgrade problems

    0.10-6+b1: amd64 arm64

    Source: cudf

  3. Package libcudf-ocaml-dev

    trixie (Debian 13 (Trixie)) (ocaml): OCaml library to access descriptions of package upgrade problems

    0.10-6+b1: amd64 arm64

    Source: cudf

Fedora 43

  1. Package ocaml-cudf

    43 (Fedora 43) (Unspecified): Format for describing upgrade scenarios

    0.10-15.fc43: aarch64 x86_64

    Source: ocaml-cudf

  2. Package ocaml-cudf-devel

    43 (Fedora 43) (Unspecified): Development files for ocaml-cudf

    0.10-15.fc43: aarch64 x86_64

    Source: ocaml-cudf

Fedora 44

  1. Package ocaml-cudf

    44 (Fedora 44) (Unspecified): Format for describing upgrade scenarios

    0.10-17.fc44: aarch64 x86_64

    Source: ocaml-cudf

  2. Package ocaml-cudf-devel

    44 (Fedora 44) (Unspecified): Development files for ocaml-cudf

    0.10-17.fc44: aarch64 x86_64

    Source: ocaml-cudf

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.