bk config(7.3ce)            BitKeeper User's Manual           bk config(7.3ce)

       bk config - show repository configuration information

       bk config [-v]

       The bk config command displays configuration information, consisting of
       key-value pairs, associated with a BitKeeper repository.

       Repository configuration information is searched for in  the  following
       places, in order:

       `bk root`/BitKeeper/etc/config     This repository's config file
       `bk root -P`/BitKeeper/etc/config  Product repository config file
       `bk dotbk`/config                  Personal config file
       /etc/BitKeeper/etc/config          Per-machine config file
       `bk bin`/config                    Per-installation config file
       `bk root`/BitKeeper/log/config     This repository's config file
       `bk root -P`/BitKeeper/log/config  Product repository config file
       $BK_CONFIG                         Environment variable

       The   BitKeeper/etc/config   file   is  version  controlled,  the  Bit-
       Keeper/log/config file is not.  Having two gives  you  a  way  to  have
       repository specific values that do not propagate.

       For  each  key-value  pair,  the first instance of a key found is used.
       You can override an earlier value  with  a  later  value,  however,  by
       appending an exclamation point to the value (not the key):

           checkout: get!

       If  multiple  instances  of  a  key  value are found with this trailing
       exclamation point, the last such value found is used.

       The BK_CONFIG environment variable may contain a list of  <key>:<value>
       pairs separated by semicolons.  For example:


       For  each repository, the various sources of configuration data collec-
       tively must specify values for at least the following keys:


       You can specify a default config file to make  setup  easier  and  more
       consistent for every repository on the system by creating a template in
       `bk dotbk`/config.template, /etc/BitKeeper/etc/config.template, or  `bk
       bin`/config.template.  If any of those files exists, bk setup automati-
       cally uses the keys in the first one found as the  BitKeeper/etc/config

       -v  Displays  the location of all config key-value pairs in the current
           configuration.  This allows you to determine which config  file  is
           controlling  each  item  in your configuration.  Items that are not
           being used because they are preceded or overridden by other  values
           are  shown  with  a  leading  pound sign (`#').  This is useful for
           debugging your configuration.

       Suppose a user is trying to determine why his keywords  are  not  being
       expanded as desired, even though he has put it in $BK_CONFIG.  "bk con-
       fig -v" shows that the his personal config file value for "keyword"  is
       taking precedence over that in $BK_CONFIG.

           $ bk config -v
           #    autofix:        no
                description:    Fred's Test repository
           #    keyword:        sccs

                keyword:        rcs!



                autofix:        yes!
           #    keyword:        sccs

       The  output also shows that the autofix value in $BK_CONFIG is overrid-
       ing the corresponding value in the repository config file  because  the
       exclamation mark is appended.

       bk config-etc
       bk config-gui


BitKeeper Inc                         1E1                     bk config(7.3ce)