Linux workstation

Upstream software project

act

Automatic Component Toolkit

About act

Automatic Component Toolkit

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

Visit project website

Project pictures and package coverage

act repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.act: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
act
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
LicenseRef-Callaway-BSD
Metadata completeness
100/100 (not a software quality rating)
Homepage
Visit upstream site
Source repository
Open source repository

Source-reported description

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

The Automatic Component Toolkit (ACT) is a code generator that takes an instance of an Interface Description Language file and generates a thin C89-API, implementation stubs and language bindings of your desired software component.

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. act

    Fedora 43 / Unspecified / source act

    1.6.0-24.fc43

    Automatic Component Toolkit

    aarch64x86_6443

Fedora 44

  1. act

    Fedora 44 / Unspecified / source act

    1.6.0-28.fc44

    Automatic Component Toolkit

    aarch64x86_6444

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.