rbm/doc/rbm-tar.asc

rbm-tar(1)
==========

NAME
----
rbm-tar - Create a tarball file


SYNOPSIS
--------
[verse]
'rbm tar' <project> [options]

DESCRIPTION
-----------

Create a tarball file for the selected project.

OUTPUT FILE
-----------

The output directory can be selected with the *output_dir* option.

The output filename will be :

 <name>-<version>.tar

If the 'compress_tar', the filename will be :

 <name>-<version>.tar.<ext>

With '<name>' the project's name, '<version>' the version of the software,
and '<ext>' the compression type selected in the 'compress_tar' option.

include::version.asc[]


CONFIGURATION OPTIONS
---------------------

The following options are related to tarball creation :

include::options_tar.asc[]

See link:rbm_config.html[rbm_config(7)] for all other options.

COMMAND LINE OPTIONS
--------------------
The command line options related to tar :

include::clioptions_tar.asc[]

See link:rbm_cli.html[rbm_cli(7)] for all other options.

Git Version
-----------

If you are going to use gpg signed commits, it is recommended to use
git >= 1.8.3.

 - git < 1.7.9 does not support signed commits. It only supports signed
   tags.

 - git < 1.8.3 does not use the +git-config+ option +gpg.program+ in
   `git log --show-signature` and `git show --show-signatures` commands
   used to check commits signatures. This means you won't be able to
   use the +gpg_keyring+ option for commits signature verification (but
   it will work for tag signature verification). This was fixed in git
   commit +6005dbb9+, included in version 1.8.3.

SEE ALSO
--------
link:rbm.html[rbm(1)]