[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

9. Multi-project Configuration Commands

9.1 build-config  instantiate a multi-project config
9.2 cat-config  output information about a multi-project config

[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

9.1 build-config

instantiate a multi-project config

usage: tla build-config [options] config

 
  -h, --help          Display a help message and exit.
  -H                  Display a verbose help message and exit.
  -V, --version       Display a release identifier string
                      and exit.
  -d, --dir DIR       cd to DIR first
  --no-pristines      don't create pristine copies
  --link              hardlink files to revision library instead of copying
  --library           ensure revisions are in the revision library
  --sparse            add library entries sparsely (--link, --library)
  -r, --release-id    overwrite ./=RELEASE-ID for this config

Build the named configuration. See also "tla cat-config -H".


[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

9.2 cat-config

output information about a multi-project config

usage: tla cat-config [options] config

 
  -h, --help        Display a help message and exit.
  -H                Display a verbose help message and exit.
  -V, --version     Display a release identifier string
                    and exit.
  -d, --dir DIR     cd to DIR first
  -o, --output CFG  write the output as config CFG
  -f, --force       overwrite an exiting config (with --output)
  -s, --snap        Show current patch levels of subtree packages.

Parse and print the indicate config file from a project tree

A config file contains blank lines, comment lines starting with "#", and config specification lines. The config file called $NAME is stored in a project tree as ./configs/$NAME or as ./$NAME.

A config specification line contains a relative path within a project tree, and a specification of the project or revision to store in that location.

For example, the line:

 
   ./src/arch   lord@emf.net--2003b/arch--devo--1.0

means that, when building the configuration, the latest revision of arch--devo--1.0 should be created within the tree as ./src/arch.

The project specification can be a branch name, version name or the name of a specific revision.

The option --snap says to examine the project tree to find out which revisions of configured project are printed, and generate a new config specification that references those specific revisions. For example, the output for the line shown above might be:

 
    ./src/arch  lord@emf.net--2003b/arch--devo--1.0--patch-21

The option --output causes the output from this command to be recorded as a new configuration file (or to replace an existing file if --force is provided).


[ << ] [ >> ]           [Top] [Contents] [Index] [ ? ]

This document was generated by wilk on May, 11 2004 using texi2html