
Upstream software project
expect
Header Files and C API Documentation for expect
About expect
Header Files and C API Documentation for expect
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
Project identity
- Project
- expect
- Publisher
- Not authoritatively mapped
- Native package records
- 4
- Operating systems
- opensuse-leap-16-0, opensuse-tumbleweed
- License expression
- SUSE-Public-Domain
- Metadata completeness
- 100/100 (not a software quality rating)
- Homepage
- Visit upstream site
- Source repository
- Not reported
Source-reported description
The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.
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.
openSUSE Leap 16.0
- expect5.45.4-160000.2.2
openSUSE Leap 16.0 / Development/Languages/Tcl / source expect
A Tool for Automating Interactive Programs
aarch64ppc64les390xx86_64leap-16.0 - expect-devel5.45.4-160000.2.2
openSUSE Leap 16.0 / Development/Libraries/Tcl / source expect
Header Files and C API Documentation for expect
aarch64ppc64les390xx86_64leap-16.0
openSUSE Tumbleweed
- expect5.45.4-8.6
openSUSE Tumbleweed / Development/Languages/Tcl / source expect
A Tool for Automating Interactive Programs
x86_64tumbleweed - expect-devel5.45.4-8.6
openSUSE Tumbleweed / Development/Libraries/Tcl / source expect
Header Files and C API Documentation for expect
x86_64tumbleweed
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.