111
98
used literally, they will be substituted by the corresponding,
112
99
platform specific, values.
114
The examples below use ':' as the separator, windows users
104
The examples below uses ':' as the separator, windows users
117
Overriding the default user plugin directory::
119
BZR_PLUGIN_PATH='/path/to/my/other/plugins'
121
Disabling the site directory while retaining the user directory::
123
BZR_PLUGIN_PATH='-site:+user'
125
Disabling all plugins (better achieved with --no-plugins)::
127
BZR_PLUGIN_PATH='-user:-core:-site'
129
Overriding the default site plugin directory::
131
BZR_PLUGIN_PATH='/path/to/my/site/plugins:-site':+user
136
Under special circumstances (mostly when trying to diagnose a
137
bug), it's better to disable a plugin (or several) rather than
138
uninstalling them completely. Such plugins can be specified in
139
the ``BZR_DISABLE_PLUGINS`` environment variable.
141
In that case, ``bzr`` will stop loading the specified plugins and
142
will raise an import error if they are explicitly imported (by
143
another plugin that depends on them for example).
145
Disabling ``myplugin`` and ``yourplugin`` is achieved by::
147
BZR_DISABLE_PLUGINS='myplugin:yourplugin'
152
When adding a new feature or working on a bug in a plugin,
153
developers often need to use a specific version of a given
154
plugin. Since python requires that the directory containing the
155
code is named like the plugin itself this make it impossible to
156
use arbitrary directory names (using a two-level directory scheme
157
is inconvenient). ``BZR_PLUGINS_AT`` allows such directories even
158
if they don't appear in ``BZR_PLUGIN_PATH`` .
160
Plugins specified in this environment variable takes precedence
161
over the ones in ``BZR_PLUGIN_PATH``.
163
The variable specified a list of ``plugin_name@plugin path``,
164
``plugin_name`` being the name of the plugin as it appears in
165
python module paths, ``plugin_path`` being the path to the
166
directory containing the plugin code itself
167
(i.e. ``plugins/myplugin`` not ``plugins``). Use ':' as the list
168
separator, use ';' on windows.
173
Using a specific version of ``myplugin``:
174
``BZR_PLUGINS_AT='myplugin@/home/me/bugfixes/123456-myplugin``
107
Overriding the default user plugin directory:
108
``BZR_PLUGIN_PATH='/path/to/my/other/plugins'``
110
Disabling the site directory while retaining the user directory:
111
``BZR_PLUGIN_PATH='-site:+user'``
113
Disabling all plugins (better achieved with --no-plugins):
114
``BZR_PLUGIN_PATH='-user:-core:-site'``
116
Overriding the default site plugin directory:
117
``BZR_PLUGIN_PATH='/path/to/my/site/plugins:-site':+user``
483
428
A publically-accessible version of this branch (implying that this version is
484
429
not publically-accessible). Used (and set) by ``bzr send``.
489
A list of strings, each string represent a warning that can be emitted by
490
bzr. Mentioning a warning in this list tells bzr to not emit it.
494
* ``format_deprecation``:
495
whether the format deprecation warning is shown on repositories that are
496
using deprecated formats.
499
432
Branch type specific options
500
433
----------------------------
508
441
~~~~~~~~~~~~~~~~~~~~~
510
443
If set to "True" then revisions can only be appended to the log, not
511
removed. A branch with this setting enabled can only pull from another
512
branch if the other branch's log is a longer version of its own. This is
513
normally set by ``bzr init --append-revisions-only``. If you set it
514
manually, use either 'True' or 'False' (case-sensitive) to maintain
515
compatibility with previous bzr versions (older than 2.2).
444
removed. A branch with this setting enabled can only pull from
445
another branch if the other branch's log is a longer version of its
446
own. This is normally set by ``bzr init --append-revisions-only``.
added
removed
bzrlib/help_topics/en/configuration.txt
