?- pack_publish('.', []).

Alternatively, an archive file has been uploaded to a public location. In this scenario we can publish the pack using

?- pack_publish(URL, [])

In both scenarios, pack_publish/2 by default creates an isolated environment and installs the package in this directory from the public URL. On success it triggers the pack server to register the URL as a new pack or a new release of a pack.

Packs may also be published using the app pack, e.g.

swipl pack publish .

Options:

git(Boolean)

If true, and Spec is a git managed directory, install using the remote repo.

sign(Boolean)

Sign the repository with the current version. This runs git tag -s <tag>.

force(Boolean)

Force the git tag. This runs git tag -f <tag>.

branch(+Branch)

Branch used for releases. Defined by git_default_branch/2 if not specified.

register(+Boolean)

If false (default true), perform the installation, but do not upload to the server. This can be used for testing.

isolated(+Boolean)

If true (default), install and build all packages in an isolated package directory. If false, use other packages installed for the environment. The latter may be used to speedup debugging.

pack_directory(+Dir)

Install the temporary packages in Dir. If omitted pack_publish/2 creates a temporary directory and deletes this directory after completion. An explict target Dir is created if it does not exist and is not deleted on completion.

clean(+Boolean)

If true (default), clean the destination directory first