pm

What curl command to use to fetch dependencies

What git command to use to fetch dependencies

Override the default package listing if a `pkgs` bundle is not currently installed.

What tar command to use to fetch dependencies

(curl & args)

Make a call to curl

(deftemplate template-name & body)

Define a inline template as defined by Python PEP292 (shell-like $ substitution),
and also allows dashes in indentifiers.

It defines new function `template-name` that takes a dictionary `opts` containing
substitutions as an argument. Keys should be keywords with the same name (sans :)
as the substitution keys.

Template is parsed from the last element of `body` which should be string and can contain substitutions.

(download-bundle url bundle-type &opt tag)

Download the package source (using git, curl+tar, or a file copy) to the local cache. Return the path to the downloaded or cached soure code.

(download-git-bundle bundle-dir url tag)

Download a git bundle from a remote respository.

(download-tar-bundle bundle-dir url)

Download a dependency from a tape archive. The archive should have exactly one top level directory that contains the contents of the project.

(git & args)

Make a call to git.

(jpm-dep-to-bundle-dep dep-name)

Convert a remote dependency identifier to a bundle dependency name. `dep-name` is any value that can be passed to `pm-install`. Will return a string than can be passed to `bundle/reinstall`, `bundle/uninstall`, etc.

(load-lockfile lock-src)

Install all saved dependencies in a lockfile.

(load-project-meta dir)

Load the metadata from a project.janet file without doing a full evaluation of the project.janet file. Returns a struct with the project metadata. Raises an error if no metadata found.

(local-hook hook & args)

Run a bundle hook on the local project.

(opt-ask key input-options)

Ask user for the value of the `key`. `input-options` should be a table with default values.
If the default value for the `key` is not `nil`, it will return that.

(pm-install bundle-code &named no-deps force-update no-install auto-remove)

Install a bundle given a url, short name, or full 'bundle code'. The bundle source code will be fetched from git or a url, then installed with `bundle/install`.

(resolve-bundle bundle)

Convert any bundle string/table to the normalized table form. `bundle` can be any of the following forms:

* A short name that indicates a package from the package listing.
* A URL or path to a git repository
* A URL or path to a .tar.gz archive
* A string of 2 parts separated by "::" - {type}::{path-or-url}
* A string of 3 parts separated by "::" - {type}::{path-or-url}::{tag}
* A table or struct with the following keys:

* `:url` or `:repo` - the URL or path of the git repository or of the .tar.gz file. Required.
* `:tag`, `:sha`, `:commit`, or `:ref` - The revision to checkout from version control. Optional.
* `:type` - The dependency type, either `:git`, `:tar`, or `:file`. The default is `:git`. Optional.

(save-lockfile lock-dest)

Create a lockfile that can be used to reinstall all currently installed bundles at a later date.

(scaffold-pm-shell path)

Generate a pm shell with configuration already setup. If `copy-janet` is truthy, the Janet executable file will be bundled in the new environment

(scaffold-project name &opt options)

Generate a standardized project scaffold.

(tar & args)

Make a call to tar.

(update-git-bundle bundle-dir tag)

Fetch latest tag version from remote repository

(vendor-binaries-pm-shell path)

Copy the Janet interpreter, shared libraries, and other installation files directly into the new shell environment. This allows
updates and changes to the system configuration without breaking the shell.