A demo implementation of how akari might be able to work ¯_(ツ)_/¯

To build and run the project use pixi.

To just build an executable to run akari-one run

$ pixi run build

Then, a binary will be available in ./target/akari-one

Or, use pixi to run cargo run

$ pixi run start -- -h

Initialize a project

$ akari init myproj

Activate that environment

$ eval "$(akari activate myproj)"

From this point, users can use pixi like they normally would. For example, add python and numpy as a dependency to the project.

$ pixi add python=3.13 numpy=2.3

Save a checkpoint by running the tag command

$ akari tag v1 --description "python 3.13 and numpy 2.3"

List available tags

$ akari list

Checkout the latest tag (determined from the git tree) of an environment

$ akari checkout latest

Deactivate the environment

$ eval "$(akari deactivate)"

List what other environments are managed by akari by running the envs command

$ akari envs ls
Available envs:
* myproj
* projmy

• Rethink how activation/deactivation of environments should work