Automic VaultAutomic Vault

brew

Installer clozure-cl avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de clozure-cl pour les workflows d'agents IA.

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install clozure-cl

local Homebrew formula metadata

aperçu

Résumé du paquet

Common Lisp implementation with a long history

historique

Historique du projet et usages

Clozure CL is a free Common Lisp implementation with roots in Macintosh Common Lisp and OpenMCL.

Historique du projet

The official history traces CCL back to Coral Software's 1984 work on Coral Common Lisp for the Macintosh. CCL 1.0 shipped in 1987 for the Macintosh Plus, then the line passed through Macintosh Allegro Common Lisp and Apple's Macintosh Common Lisp.

Apple transferred MCL to Digitool in 1994 during the PowerPC transition, and Digitool released a PowerPC version around 1995. A JPL effort later licensed MCL source for PowerPC robotics and flight-system work; Gary Byers ported the compiler and runtime to VxWorks and LinuxPPC in 1998.

Digitool agreed in 2001 to open source the JPL work, creating OpenMCL. In 2007, OpenMCL was renamed Clozure CL to avoid confusion with the newly open sourced original MCL code.

Historique d'adoption

The official site describes Clozure CL as available across macOS, Linux, FreeBSD, illumos, and Windows, which made it a portable Common Lisp for users who wanted native threads, fast compilation, a compacting generational garbage collector, and a foreign-function interface.

For package managers, Clozure CL matters as a long-lived Lisp runtime that exposes a simple `ccl64` executable while carrying decades of Mac Lisp lineage into Unix-style packaging.

Modes d'utilisation

Users run `ccl64` for the Clozure CL listener/compiler and can build CCL from source using an already-working CCL, because the implementation is written in itself.

The project documents user support through the ccl-devel mailing list, IRC, GitHub issues, and release downloads from GitHub.

Pourquoi les passionnés de paquets s'y intéressent

Clozure CL is unusually interesting to package maintainers because it is self-hosting, historically tied to Macintosh Lisp, and packaged as a full language runtime rather than a small utility.

Its init-file behavior and architecture-specific binaries are the sort of details that make Lisp implementations visible in Homebrew and other Unix packaging ecosystems.

Chronologie

  • 1984: Coral Software began Coral Common Lisp for the Macintosh.
  • 1987: CCL 1.0 was released for a 1 MB Macintosh Plus.
  • 1988: Coral was acquired by Apple, and the Lisp became Macintosh Common Lisp.
  • 1994: Apple transferred MCL to Digitool.
  • 1998: A JPL-backed port of the MCL compiler and runtime reached VxWorks and LinuxPPC.
  • 2001: Digitool agreed to open source the JPL work, creating OpenMCL.
  • 2007: OpenMCL was renamed Clozure CL.
  • 2017: GitHub releases include Clozure CL 1.11.

Related projects

  • Coral Common Lisp, Macintosh Allegro Common Lisp, Macintosh Common Lisp, and OpenMCL are direct predecessors in the official history.
  • CCLDoc is the documentation format/project referenced by the official Clozure CL site.

posture de sécurité

Niveau de risque : vert

narrow executable package without higher-risk signals.

Classificateur de risque

risque vert · confiance faible · appliance

Pourquoi

  • narrow executable package without higher-risk signals

Signaux

  • metadata:no-higher-risk-signals

Comportement d'installation

  • Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
  • Les métadonnées de bottle Homebrew sont disponibles pour 4 plateformes.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
~/ccl-init.lisp~/.ccl-init.lisp

exécutables

Exécutables installés

CommandeTypeExpositionNote
ccl64cliexécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-08
version du gestionnaire1.13
gestionnaire mis à jour
données localesOK
amontà jour
dernière version détectéev1.13

https://github.com/Clozure/ccl

  • infoNo package-manager update timestamp was available.confiance faible

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:clozure-cl
Version1.13
Gestionnaire de paquetsHomebrew
Page du gestionnaire de paquetshttps://formulae.brew.sh/formula/clozure-cl
Page d'accueilhttps://ccl.clozure.com
Dépôthttps://github.com/Clozure/ccl
Docs amonthttps://ccl.clozure.com/docs
LicenceApache-2.0
Archive sourcehttps://github.com/Clozure/ccl/archive/refs/tags/v1.13.tar.gz
Bouteilledisponible (sur monterey, sonoma, ventura, x86_64_linux)
post-install Homebrewnon défini
Serviceaucun déclaré

faits du registre

Détails de la base source

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameclozure-cl
Version Scheme0
Revision0
Head VersionHEAD
Requirements
  • arch
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedyes
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment