Monticello (file format)

Monticello (file format). The Monticello file format is a specialized serialization and version control format designed primarily for the Smalltalk programming environment. It serves as a container for source code, metadata, and change history, enabling collaborative development and package management within projects like Squeak and Pharo. The format is named after the Monticello estate of Thomas Jefferson, reflecting its architectural approach to organizing code components.

Overview

Monticello files, typically with the .mcz extension, function as archives bundling software packages or code units. The format is integral to the Monticello versioning system, a tool used extensively within the Smalltalk community for managing object-oriented code snapshots. Unlike generic version control systems like Git or Subversion, Monticello is deeply integrated with the Smalltalk image paradigm, tracking changes to classes and methods directly. Its design facilitates distributed development and simplifies the process of software distribution and dependency management among developers.

Technical details

A Monticello file is essentially a ZIP archive containing a structured collection of text files and JSON metadata. The core component is a version file detailing the package name, author, timestamp, and ancestor version information, following a directed acyclic graph model for history. The source code is stored in Chunk format, a plain text representation of Smalltalk syntax that includes definitions for classes, methods, and extensions. The format also supports patches (diffs) between versions and includes a manifest file cataloging all contents. SHA-1 hashes are used for data integrity verification, and the entire package is MIME-typed as `application/x-monticello`.

History and development

The Monticello format was created in 2006 by Avi Bryant, then of Cincom Systems, with significant contributions from Jens von Pilgrim and Lukas Renggli. It was developed to address limitations in earlier Smalltalk code management tools like Envy and Store, providing a simpler, file-based alternative for the then-emerging Squeak and Pharo platforms. The system was first presented at the European Smalltalk Users Group conference and quickly became a standard. Its development was closely tied to the Seaside web framework project, which required robust package management. Subsequent tooling, like the Metacello configuration framework, built upon Monticello to manage complex dependency graphs.

Usage and adoption

Monticello is the de facto package format for the Pharo and Squeak ecosystems, used for distributing libraries, frameworks, and applications through repositories like SmalltalkHub and GitHub. Development environments like Pharo Launcher and Moose use it for project loading and version switching. While its adoption is largely confined to the Smalltalk world, it has been critical for projects such as Seaside, Glamorous Toolkit, and PolyMath. The format is supported by client tools within the Smalltalk image and by server-side systems like Monticello Server and Squot.

Related formats

Monticello is often compared to and interacts with other software deployment and versioning formats. The FileTree format, also used in Pharo, stores code directly in the file system as directories of text files, offering better compatibility with Git. Metacello uses configuration files (`.ston` or `.mc`) to describe dependencies on Monticello packages. Outside Smalltalk, analogous systems include Java's JAR files, NuGet packages for .NET, and RubyGems for Ruby. The Chunk format itself is a precursor to modern structured storage approaches in IDEs.