4
A configuration option has:
6
* a name: a valid python identifier (even if it's not used as an
7
identifier in python itself)
9
* a value: a unicode string or a list of unicode strings.
7
As a Bazaar developer there are a few things you need to know about
10
* how to add a new option,
12
* how add a new stack,
14
* how add a new store.
16
The first sections in this document summarize the steps needed when adding a
17
new configuration item, the rest of the document gives more internal details
18
on how this is implemented.
23
Options values are obtained with ``stack.get(option_name)`` where ``stack``
24
is one of the daughter classes of ``config.Stack``, see their docstrings for
25
a description of which sections are used from which stores.
27
The value returned is of the type declared for that ``Option`` and if
28
nothing is specifically declared you will get the default for that option.
33
You add a new ``Option`` to the ``option_registry``, either inside
34
``bzrlib/config.py`` or during initialization of your plugin (use
35
``register_lazy`` in this case). New plugins should have systematic
36
hierarchical names so that related values are grouped together::
38
option_registry.register(
39
Option('dirstate.fdatasync', default=True,
40
from_unicode=bool_from_store,
41
help="Flush dirstate changes onto physical disk? ...."))
43
You then need to decide which stack is appropriate to implement the Option
46
* which config files (aka ``Store``) needs to be queried, which sections are
47
relevant and in what order,
49
* which section will receive the modifications (if relevant).
51
The docstrings for the existing stacks cover most of the known use cases.
53
Modify an option value or delete an option
54
------------------------------------------
56
Just reading an option is what is needed most of the time, modifying option
57
values or removing options is usually something that is not automated but
58
left to the user (with ``bzr config``).
60
Nevertheless, if you need to save a modified option value, use
61
``.set(option_name, value)`` and ``.remove(option_name)`` to delete the
62
option. Both methods are provided by the ``Stack`` object.
64
But before doing that, you must be sure that the stack you're using have a
65
writable section (this is true for ``GlobalStack`` which uses the
66
``DEFAULT`` section in ``bazaar.conf`` and for ``BranchStack``which uses the
67
no-name section in ``branch.conf``).
69
Old and new configuration code
70
------------------------------
72
There is (as of late 2011) some older and some newer configuration code. The
73
old code has specific methods for various checks or uses classes like
74
``GlobalConfig``. Don't add to to it; try to remove it.
76
If you encounter an option using the old code you may want to migrate
77
it. This generally involves:
79
* registering the option,
81
* replace the old config by a stack:
83
* ``GlobalConfig`` became ``GlobalStack``,
85
* ``LocationConfig`` became ``LocationStack``,
87
* ``BranchConfig`` became ``BranchStack`` (or in this case,
88
``get_config()`` became ``get_config_stack()``.
90
* replace the custom accessor calls with ``conf.get(option_name)``.
92
The new config code provides some help for commonly encountered use cases
93
that can allow further simplifications like:
95
* providing a default value when the option is not defined in any way by the
98
* convert the unicode string provided by the user into a suitable
99
representation (integer, list, etc).
104
Stacks capture the various places an option can be declared by the user with
105
associated levels of generality and query them in the appropriate order
106
returning the first definition found. For example, the
107
``append_revisions_only`` option may be declared for all branches of a user
108
in ``bazaar.conf``, or for a hierarchy of branches in ``locations.conf`` or
109
in a single branch in ``branch.conf``.
111
Defining a new stack means you need a new way to expose these levels to the
112
user that is not covered by the existing stacks.
114
This is achieved by declaring:
116
* which stores can provide a value for the option,
118
* which sections apply to the stack instance, some filtering for a given
119
context can be defined,
121
* which (store, section) should receive the modifications.
123
Mapping different sections to different stacks is a powerful way to organize
124
the options and provide various levels of configuration to the user. This is
125
achieved with ``Store`` and ``SectionMatcher`` objects.
131
The following stores are used by ``bzr`` in ways that illustrate various
137
``bzr`` itself defines two sections here:
139
* ``DEFAULT`` where global options are defined,
141
* ``ALIASES`` where command aliases are defined. This section is *not*
142
available via ``GlobalStack``, instead, the ``bzr alias`` command uses it
143
for its own purposes.
145
Plugins can define either additional options in the ``DEFAULT`` section or
146
new sections for their own needs (this is not especially encouraged
147
though). The ``bzr-bookmarks`` plugin defines a ``BOOKMARKS`` section there
153
The Ubuntu package importer defines a store and two stacks involving
154
``pkgimport.conf``. A no-name section contains the options common to all
155
packages and sections named after their corresponding package can also be
158
The ``ImporterStack`` uses ``locations.conf`` and the no-name section in
159
``pkgimport.conf`` for the importer options.
161
The ``PackageStack`` uses only ``pkgimport.conf`` and uses the section name
162
after the package followed by the no-name section.
167
``bzr`` defines sections corresponding to URLs there and includes the
168
relevant sections in ``LocationStack`` and ``BranchStack``. No no-name
169
section is recognized in this file.
174
This file defines the option for a given branch and uses only the no-name
89
281
Only ``ReadOnlySection`` objects are manipulated here but a
90
282
``SectionMatcher`` can return dedicated ``Section`` objects to provide
91
283
additional context (the ``LocationSection`` add an ``extra_path`` attribute
92
to implement the ``appendpath`` policy for example). If no sections match,
284
to implement the section local options for example). If no sections match,
93
285
an empty list is returned.
95
.. FIXME: Replace the appendpath example if/when it's deprecated ;)
287
Options local to a section can be defined for special purposes and be
288
handled by ``Section.get()``. One such option is ``relpath`` which is
289
defined in ``LocationSection`` as an alternative to the ``appendpath``
292
For ``appendpath``, the ``LocationSection`` will carry ``extra_path`` as the
293
relative path between the section name and the location used. ``relpath``
294
will be available as a ``Section`` local option with the same
295
value. ``basename`` will carry the location base name and be available as a
296
local option with the same name. Note that such options can only be expanded
297
inside the section that defines them.
97
299
Specific section matchers can be implemented by overriding ``get_sections``
98
300
or just ``match``.
100
302
``bzrlib`` provides:
102
* ``LocationMatcher(store, location)``: To select all sections that match
105
304
* ``NameMatcher(store, unique_id)``: To select a single section matching
307
* ``LocationMatcher(store, location)``: To select all sections that match
308
``location`` sorted by decreasing number of path components.
310
* ``StartingPathMatcher(store, location)``: To select all sections that
311
match ``location`` in the order they appear in the ``store``.
111
An option can take different values depending on the context it is used. Such
112
a context can involve configuration files, options from the command line,
316
An option can take different values depending on the context it is
317
used. This can involve configuration files, options from the command line,
113
318
default values in bzrlib and then some.
115
320
Such a context is implemented by creating a list of ``Section`` stacked upon
added
removed
doc/developers/configuration.txt
