/brz/remove-bazaar

To get this branch, use:
bzr branch http://gegoxaren.bato24.eu/bzr/brz/remove-bazaar

« back to all changes in this revision

Viewing changes to doc/en/user-guide/writing_a_plugin.txt

  • Committer: Martin Pool
  • Date: 2010-10-08 04:38:25 UTC
  • mfrom: (5462 +trunk)
  • mto: This revision was merged to the branch mainline in revision 5478.
  • Revision ID: mbp@sourcefrog.net-20101008043825-b181r8bo5r3qwb6j
merge trunk

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/en/user-guide/writing_a_plugin.txt
22
22
``bzrlib.commands.register_command(cmd_foo)``.  You must register the
23
23
command when your file is imported, otherwise bzr will not see it.
24
24
 
 
25
Installing a hook
 
26
-----------------
 
27
 
 
28
See `Using hooks`_.
 
29
 
 
30
 .. _Using hooks: hooks.txt
 
31
 
 
32
 
25
33
Specifying a plugin version number
26
34
----------------------------------
27
35
Simply define ``version_info`` to be a tuple defining the current version
34
42
 
35
43
Bzr will scan ``~/.bazaar/plugins``  and ``bzrlib/plugins`` for plugins
36
44
by default.  You can override this with  ``BZR_PLUGIN_PATH``
37
 
(see `User Reference <../user-reference/bzr_man.html#bzr-plugin-path>`_
38
 
for details).
 
45
(see `User Reference 
 
46
<../user-reference/configuration-help.html#bzr-plugin-path>`_ for details).
39
47
 
40
48
Plugins may be either modules or packages.  If your plugin is a single
41
49
file, you can structure it as a module.  If it has multiple files, or if