Upstream software project

SAASound

Development files for SAASound

About SAASound

Development files for SAASound

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.SAASound: recorded package coverageFedora 432 recordsFedora 442 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
SAASound
Publisher
Not authoritatively mapped
Native package records
4
Operating systems
fedora-43, fedora-44
License expression
LicenseRef-Callaway-BSD
Source repository
Not reported

Source-reported description

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

Phillips SAA 1099 sound chip emulator library

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 SAASound

    43 (Fedora 43) (Unspecified): Phillips SAA 1099 sound chip emulator library

    3.2-40.fc43: aarch64 i686 x86_64

    Source: SAASound

  2. Package SAASound-devel

    43 (Fedora 43) (Unspecified): Development files for SAASound

    3.2-40.fc43: aarch64 i686 x86_64

    Source: SAASound

Fedora 44

  1. Package SAASound

    44 (Fedora 44) (Unspecified): Phillips SAA 1099 sound chip emulator library

    3.2-42.fc44: aarch64 i686 x86_64

    Source: SAASound

  2. Package SAASound-devel

    44 (Fedora 44) (Unspecified): Development files for SAASound

    3.2-42.fc44: aarch64 i686 x86_64

    Source: SAASound

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.