Home / Docs / Specification
30. Packages and dependencies
Status: Normative, edition 0.4 preview (ADR 0122).
From edition 0.4, a package describes itself in ita.una, a declarative file in Una's lexical syntax, and is pinned by ita.lock, which only the tool writes. A repository may group packages in a workspace with itaty.una. Itá, the package manager, is the command una ita of the una binary. The rules of ADR 0122 join this chapter as they land, each with its conformance cases. A package loads its path dependencies (§12) and the releases of the sources its sources section declares, verified by the registry client (§14); every other need is refused (U7008), so no import ever reaches a package that is not checked with the program.
Editions. The rules of this chapter apply only to packages of edition 0.4 and later. Editions 0.1 to 0.3 keep una.toml and verification.lock (spec/13 §7), and a single file has no dependencies. A single file keeps edition 0.1, except that a file named to una fmt, una check or another command, with an ita.una or una.toml in a directory above it, is read, formatted and checked in the edition of the nearest such manifest and is otherwise still its own package (#1175).
Sections
- 30.1 Lexical rules
- 30.2 ita.una
- 30.3 Needs and sources
- 30.4 ita.lock
- 30.5 Workspaces: itaty.una
- 30.6 Commands
- 30.7 The proof cache
- 30.8 Migration: una migrate
- 30.9 Package content, digest and archive
- 30.10 Versions and resolution
- 30.11 Verifying a registry's documents
- 30.12 Path dependencies in the program
- 30.13 Trust a dependency adds
- 30.14 The registry client
- 30.15 Publishing, yanks, audit, watch and bundles
- 30.16 The registry service