1
Location of configuration file
2
==============================
3
Each user gets a pair of configurations files in $HOME/.bazaar. The first
4
one, named bazaar.conf, includes default configuration options. The other
5
file, locations.conf, contains configuration information for specific
10
An ini file has three types of contructs: section headers, section
11
variables and comments.
15
A comment is any line that starts with a "#" (sometimes called a "hash
16
mark", "pound sign" or "number sign"). Comment lines are ignored by
17
Bazaar-NG when parsing ini files.
21
A section header is a word enclosed in brackets that starts at the begining
22
of a line, typical section headers look like this::
26
The only valid section header for bazaar.conf is [DEFAULT], which is case
27
senstive. The default section provides for setting variables which can be
28
overridden with the branch config file.
30
For locations.conf, the variables from the section with the longest matching
31
section header are used to the exclusion of other potentially valid section
32
headers. A section header uses the path for the branch as the section
33
header. Some examples include::
35
[http://mybranches.isp.com/~jdoe/branchdir]
36
[/home/jdoe/branches/]
43
A section variable resides within a section. A section variable contains a
44
variable name, an equals sign and a value and generally takes the following
47
email = John Doe <jdoe@isp.com>
48
check_signatures = require
51
The main configuration file, bazaar.conf
52
----------------------------------------
54
The main configuration file, $HOME/.bazaar/bazaar.conf, only allows one
55
section called '''[DEFAULT]'''. This default section contains the default
56
configuration options for all branches. The default section can be
57
overriden by providing a branch specific section in locations.conf.
59
A typical bazaar.conf section often looks like the following::
62
email = John Doe <jdoe@isp.com>
64
check_signatures = check-available
65
create_signatures = when-required
67
$HOME/.bazaar/locations.conf allows one to specify overriding settings for a
68
specific branch. The format is almost identical to the default section in
69
bazaar.conf with one significant change: The section header, instead of
70
saying default, will be the path to a branch that you wish to override a
71
value for. The ? and * wildcards are supported::
73
[/home/jdoe/branches/nethack]
74
email = Nethack Admin <nethack@nethack.com>
76
[http://hypothetical.site.com/branches/devel-branch]
77
create_signatures = always
78
check_signatures = always
80
[http://bazaar-ng.org/bzr/*]
81
check_signatures = require
83
Common Variable options
84
=======================
88
The email address to use when committing a branch. Typically takes the form
91
email = Full Name <account@hostname.tld>
95
The path of the editor that you wish to use if *bzr commit* is run without
96
a commit log message. This setting is trumped by the environment variables
97
$BZREDITOR or $EDITOR.
101
Defines the behavior for signatures.
104
the gnupg signature for revisions must be present and must be valid
107
Do not check gnupg signatures of revisions.
110
(default) If gnupg signatures for revisions are present, check them.
111
Bazaar-NG will fail if it finds a bad signature, but will not fail if
112
no signature is present
116
Defines the behaviour of signing revisions. Has three possible values:
117
always, never and when-requied.
120
sign every new revision that is committed
123
(default) Sign newly committed revisions only when the branch requires
127
Refuse to sign newly committed revisions, even if the branch requires signatures
131
Only useful in locations.conf. Defines whether or not the configuration for
132
this section applies to subdirectories:
135
(default) This section applies to subdirectories as well
138
This section only applies to the branch at this directory and not
143
(Default: "gpg"). Which program should be used to sign and check revisions.
146
gpg_signing_command = /usr/bin/gnpg
added
removed
doc/configuration.txt
