
Upstream software project
gnuplot-iostream
C++ programming interface for gnuplot. Docs and examples
About gnuplot-iostream
C++ programming interface for gnuplot. Docs and examples
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
- gnuplot-iostream
- Publisher
- Not authoritatively mapped
- Native package records
- 4
- Operating systems
- debian-12, debian-13
- License expression
- Not reported
- Metadata completeness
- 80/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.
Debian 12 (Bookworm)
- libgnuplot-iostream-dev0~20140302.gitc8919a0+dfsg-4
Debian 12 (Bookworm) / libdevel / source gnuplot-iostream
C++ programming interface for gnuplot. Headers
allbookworm - libgnuplot-iostream-doc0~20140302.gitc8919a0+dfsg-4
Debian 12 (Bookworm) / doc / source gnuplot-iostream
C++ programming interface for gnuplot. Docs and examples
allbookworm
Debian 13 (Trixie)
- libgnuplot-iostream-dev0~20140302.gitc8919a0+dfsg-4
Debian 13 (Trixie) / libdevel / source gnuplot-iostream
C++ programming interface for gnuplot. Headers
alltrixie - libgnuplot-iostream-doc0~20140302.gitc8919a0+dfsg-4
Debian 13 (Trixie) / doc / source gnuplot-iostream
C++ programming interface for gnuplot. Docs and examples
alltrixie
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.