15.5.2.2 Publishing a pack
As described in section
15.4, a pack is distributed either as an archive file or as a GIT
repository. We strongly encourage using a GIT repository as that gives
good version and provenance support. Packs may be published by hand by
making the archive or git repository available from a globally
accessible place on the internet and installing the pack from this
location. This process is streamlined, notably for GIT packs using pack_publish/2
and the
app pack
. To publish a pack a local GIT repository
that has publicly accessible origin,
- Update
version(Version)
inpack.pl
- Commit all changes, make sure the the repository is clean.
- Run
swipl pack publish .
This will
- Verify the repository is clean and on the default branch.
- Tag the repository with V<version>. By default, the tag will be signed. Please setup signing for GIT or use the “--no-sign`` option.
- Push the repository and release tag.
- Figure out the download location, either from the
download(URL)
metadata or the GIT remote information. - Install the package and its dependencies in a temporary isolated pack environment.
- On success, register the pack with the server.
- Delete the isolated pack environment.
Similarly, a pack can be published from a public archive using the command below. When using an archive, never change the content of the archive but, instead, create a new archive with a new version.
swipl pack publish URL