Tools

Packages and projects

Every Genzimnify project can describe itself and its dependencies in gzim.toml. Packages may come from Git or a local directory.

Create a project

mkdir my-vibe && cd my-vibe
gzim init

This creates main.gzim and a manifest:

[project]
name = "my-vibe"
version = "0.1.0"

[dependencies]

Add a dependency

gzim add cool https://github.com/example/cool.git
gzim add pinned https://github.com/example/pinned.git#v1.4.0
gzim add local ../my-local-package

The command records the source and installs it under the project-local .gzim/packages/ cache. A #tag, #branch, or #commit selects the revision for the first install or an explicit update. Subsequent installs use the resolved commit in the lockfile.

Restore dependencies

gzim install

Reads gzim.toml and restores every dependency. Resolved Git commits are recorded in gzim.lock so another machine installs the same code. Commit both files; do not commit .gzim/.

Update and strict installs · 2.0.6

gzim install --locked
gzim update cool
gzim update

--locked requires a lockfile matching every manifest dependency and does not rewrite it. Locked commits take precedence over branch and tag names. update cool refreshes only that package; update refreshes all packages using their configured source references. All downloads finish before any installed package is replaced. Fetch failures preserve installed packages and the lockfile. Local path dependencies are copied from their current contents; their lock entry records the path source, not a content snapshot.

Use a package

pull up cool
yap(call up cool.greet("world") yo)

A package can expose cool.gzim, src/cool.gzim, nested modules, or main.gzim.

List and remove

gzim packages
gzim remove cool
Package sources

Genzimnify accepts Git repositories and local directories as package sources. Package updates are staged before replacing an installed dependency. A central package registry is not implemented.