"janet" depends on

build (1)

Ports that depend on "janet"

Port notes

Janet has a package ecosystem (similar to how Nodejs does) and these packages are managed by the package manager jpm. However jpm is not installed by default. You have a few options which are not mutually exclusive.

In both cases MacPorts will install jpm itself but you can then choose whether or not to use globally installed jpm packages as in (1) and/or you can install local versions of jpm packages as in (2) using the --local flag of jpm.

(1) Use jpm packages managed by MacPorts. These are available with prefix 'janet-' so the package 'joy' is on MacPorts as 'janet-joy' etc.

e.g.
$ port install janet-joy

(2) Use jpm packages via jpm itself. It is _not_ recommended to install packages globally as they would be unmanaged by MacPorts meaning if you uninstall jpm these files would remain on disk and not be cleaned up as you might expect. Luckily jpm has functionality to install packages into a custom directory (e.g. local to your janet project). This is toggled via the --local flag when invoking jpm See the installation notes for jpm for more information beyond the basic example below.

e.g.
$ port install jpm
$ cd ~/projects/foo && jpm install --local joy

Note: use of sudo in the above commands depends on whether your MacPorts is installed to a directory owned by the root user.