Usage 1: ${command} [OPTION...] APP_DIR
Create a package for a Palm webOS containing a single application.

Usage 2: ${command} [OPTION...] PKG_DIR [APP_DIR] [SERVICE_DIR...] [ACCOUNT_DIR...]
Create a package for a Palm webOS containing an application and/or services and accounts.

Options:
    --check                    Check the application but don't package it
-o, --outdir=OUTPUT_DIR        Use OUTPUT_DIR as the output directory
    --exclude=PATTERN          Exclude files, given as a PATTERN
-X, --exclude-from=PATFILE     Exclude patterns listed in PATFILE
    --ignore-case              Ignore case when matching names
    --no-exclude-eclipse       Don't exclude Eclipse meta-data
    --no-exclude-hidden        Don't exclude hidden files
    --no-exclude-vcs           Don't exclude version control meta-data
    --no-exclude-ipk           Don't exclude .ipk files
-p, --property=PROPERTY        Set the property PROPERTY
    --use-v1-format            Generate packages in old format (apps only)
    --version                  Display version info and exit
    --help                     Display this help and exit

APP_DIR is an application directory containing a valid appinfo.json file.
Only one application directory is allowed.

PKG_DIR is a package info directory containing a valid packageinfo.json file.
Only one package info directory is allowed.

SERVICE_DIR is a service directory containing a valid services.json file.

ACCOUNT_DIR is a account directory containing a valid account-templates.json file.

OUTPUT_DIR is the output directory where the package will be created. If not
specified, the current directory is used.

PATTERN is a name-matching string which may contain the wildcards * and ?.
Matching is case-sensitive unless the --ignore-case option is used.

PATFILE is a text file with one PATTERN per line.
Matching is case-sensitive unless the --ignore-case option is used.

By default, ${command} will exclude meta-data files used by Eclipse plugins.
Use the --no-exclude-eclipse option to include these files.

By default, ${command} will exclude hidden files.
Use the --no-exclude-hidden option to include these files.

By default, ${command} will exclude meta-data files used by following version
control systems: CVS, RCS, SCCS, SVN, Arch, Bazaar, Mercurial, and Darcs.
Use the --no-exclude-vcs option to include these files.

By default, ${command} will exclude ipk files.
Use the --no-exclude-ipk option to include these files.

PROPERTY defines properties to be used during package creation. Properties can be
specified as key-value pairs of the form "key=value" or as JSON objects of the
form "{'key1':'value1', 'key2':'value2', ...}". Surrounding quotes are required
in both cases.

If not specified, the package id and package version will be derived from the
id and version properties in the application's appinfo.json file.

The filename of the newly created package will be derived from the package id and
package version.

Note: To create a package compatible with earlier versions of the app catalog,
use the "--use-v1-format" option. Only single-app packages (usage 1) are supported.

Examples:

# Create a package for the Palm application in ~/projects/Ticker.
${command} ~/projects/Ticker

# Create a package for the Palm application in ~/projects/Ticker and set the
output directory to ~/packages.
${command} -o ~/packages ~/projects/Ticker

# Create a package for the Palm application in ~/projects/Ticker. Exclude all
text files and the tests directory.
${command} --exclude="*.txt" --exclude="tests" ~/projects/Ticker

# Create a package for a Palm application and service.
${command} ticker-info ticker-app ticker-service
