1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
Using plugins
=============
.. Information on how to use plugins in Breezy.
What is a plugin?
-----------------
A plugin is an external component for Breezy that is typically made by
third parties. A plugin is capable of augmenting Breezy by adding new
functionality. A plugin can also change current Breezy behavior by
replacing current functionality. Sample applications of plugins are:
* overriding commands
* adding new commands
* providing additional network transports
* customizing log output.
The sky is the limit for the customization that can be done through plugins.
In fact, plugins often work as a way for developers to test new features for
Breezy prior to inclusion in the official codebase. Plugins are helpful
at feature retirement time as well, e.g. deprecated file formats may one
day be removed from the Breezy core and be made available as a plugin instead.
Plugins are good for users, good for external developers and good for
Breezy itself.
Where to find plugins
---------------------
We keep our list of plugins on the http://wiki.bazaar.canonical.com/BzrPlugins page.
How to install a plugin
-----------------------
Installing a plugin is very easy! If not already created, create a
``plugins`` directory under your Breezy configuration directory,
``~/.bazaar/`` on Unix and
``C:\Documents and Settings\<username>\Application Data\Breezy\2.0\``
on Windows. Within this directory (referred to as $BZR_HOME below),
each plugin is placed in its own subdirectory.
Plugins work particularly well with Breezy branches. For example, to
install the brztools plugins for your main user account on GNU/Linux,
one can perform the following::
brz branch http://panoramicfeedback.com/opensource/brz/brztools
~/.bazaar/plugins/brztools
When installing plugins, the directories that you install them in must
be valid python identifiers. This means that they can only contain
certain characters, notably they cannot contain hyphens (``-``). Rather
than installing ``brz-gtk`` to ``$BZR_HOME/plugins/brz-gtk``, install it
to ``$BZR_HOME/plugins/gtk``.
Alternative plugin locations
----------------------------
If you have the necessary permissions, plugins can also be installed on a
system-wide basis. One can additionally override the personal plugins
location by setting the environment variable ``BZR_PLUGIN_PATH`` (see `User
Reference <../user-reference/configuration-help.html#brz-plugin-path>`_
for a detailed explanation).
Listing the installed plugins
-----------------------------
To do this, use the plugins command like this::
brz plugins
The name, location and version of each plugin installed will be displayed.
New commands added by plugins can be seen by running ``brz help commands``.
The commands provided by a plugin are shown followed by the name of the
plugin in brackets.
Popular plugins
---------------
Here is a sample of some of the more popular plugins.
================ ================= ==================================
Category Name Description
================ ================= ==================================
GUI QBzr Qt-based GUI tools
GUI brz-gtk GTK-based GUI tools
GUI brz-eclipse Eclipse integration
General brztools misc. enhancements including shelf
General difftools external diff tool helper
General extmerge external merge tool helper
Integration brz-svn use Subversion as a repository
Migration cvsps migrate CVS patch-sets
================ ================= ==================================
If you wish to write your own plugins, it is not difficult to do.
See `Writing a plugin <writing a plugin.html>`_ in the appendices to get
started.
|