Chapter 8. Publishing packages on a web site

Table of Contents

1. Creating GPG keys
2. Creating a primary repository
3. Creating packages for publishing
4. Updating the repository metadata
5. Creating a remote repository
6. Synchronizing remote repositories
7. Installing packages from remote repositories

LPMtool makes it easy to distribute packages on a web site. The lpm(1) manual page describes all the available bells and whistles. This chapter gives a simplified overview of how to set up a simple web site that distributes LPMtool packages, and how to automatically download packages from a web site. The steps involved are:

This takes care of publishing packages on a web site. The steps to download packages from a web site are even shorter:

1. Creating GPG keys

GPG keys provide a way to verify package files downloaded from a web site. Run the gpg command to create a new GPG key, if necessary. Of course, an existing GPG key will work just as well:

gpg --gen-key

The GPG key must be exported to a file (the following examples use pgpkeys.txt) using the --armor option:

gpg --export --armor -o gpgkey.txt

This command exports all public GPG. It is possible to use multiple GPG keys with a published primary repository, and any one of the keys may be used to publish packages. Otherwise, use --default-key to specify a single GPG key.


The exported GPG key must be the default secret key which will be used to sign packages.