unperish(1)
NAME
unperish - release free software projects
SYNOPSIS
unperish [options] operation ...
DESCRIPTION
unperish automates the repetitive and mechanical parts of doing a
release of a free software project. For example, it can create the
official release tar-file, then build Debian source and binary packages
based on that. It does not take care of things that inherently require
manual effort, such as updating a NEWS file or writing the packaging
files for Debian packages.
unperish is quite flexible. Each step in the process is implemented by
an operation, such as build-tarball-from-bzr, which creates the official release tar-file from a Bazaar (bzr) branch. Each of the operations is provided by a plugin, so that different projects can adapt the
tool to its needs. For example, a project that uses another version
control system might use (or write) a plugin for creating the release
tar file using the export command for that system. The other steps to
do the release, which don't care about where the tar file came from,
are then independent from the version control system used.
To get a description of all operations, use the list operation. To get
help on command line options, use the --help option.
ENVIRONMENT
- UNPERISH_PLUGINS
- If set, must be a colon separated list of directories (like PATH) in which to search for plugin files. This completely overrides the built-in list.
FILES
- /usr/share/unperish/plugins
- Location for plugins that are installed as part of the unperish program. Also, additional plugins installed via a packaging system should go here.
- /usr/local/share/unperish/plugins
- System-wide location for additional plugins, not installed via a packaging system. A system administrator might install plugins here if they want to make them included for everyone.
- ~/.unperish/plugins
- The user's own plugins.
AUTHOR
- Lars Wirzenius (liw@iki.fi).