Upstream software project

cl-iterate

Jonathan Amsterdam's Common Lisp iterator/gatherer/accumulator facility

About cl-iterate

Jonathan Amsterdam's Common Lisp iterator/gatherer/accumulator facility

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.

Project pictures and package coverage

Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records. Catalog coverage diagram, not an application screenshot.cl-iterate: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
cl-iterate
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
debian-12, debian-13
License expression
Not reported
Source repository
Not reported

Source-reported description

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

Jonathan Amsterdam's Common Lisp iterator/gatherer/accumulator facility

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 12 (Bookworm)

  1. Package cl-iterate

    bookworm (Debian 12 (Bookworm)) (lisp): Jonathan Amsterdam's Common Lisp iterator/gatherer/accumulator facility

    20210519.gitb0f9a9c-1: all

Debian 13 (Trixie)

  1. Package cl-iterate

    trixie (Debian 13 (Trixie)) (lisp): Jonathan Amsterdam's Common Lisp iterator/gatherer/accumulator facility

    20231229.git26cf129-2: all

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.