1
Exporting version information
2
=============================
4
Getting the last revision number
5
--------------------------------
7
If you only need the last revision number in your build scripts, you can
8
use the ``revno`` command to get that value like this::
14
Getting more version information
15
--------------------------------
17
The ``version-info`` command can be used to output more information
18
about the lastest version like this::
21
revision-id: pqm@pqm.ubuntu.com-20071211175118-s94sizduj201hrs5
22
date: 2007-12-11 17:51:18 +0000
23
build-date: 2007-12-13 13:14:51 +1000
27
You can easily filter that output using operating system tools or
28
scripts. For example (on Linux/Unix)::
30
$ bzr version-info | grep ^date
31
date: 2007-12-11 17:51:18 +0000
33
The ``--all`` option will actually dump version information about
34
every revision if you need that information for more advanced
41
.. TODO: Figure out how to attach into ``setup.py``
44
If using a Makefile to build your project, you can generate the version
45
information file as simply as::
48
bzr version-info --format python > library/_version.py
50
This generates a file which contains 3 dictionaries:
52
* `version_info`: A dictionary containing the basic information about the
55
* `revisions`: A dictionary listing all of the revisions in the
56
history of the tree, along with the commit times and commit
57
message. This defaults to being empty unless ``--all`` or
58
``--include-history`` is supplied. This is useful if you want to
59
track what bug fixes, etc, might be included in the released
60
version. But for many projects it is more information than needed.
62
* `file_revisions`: A dictionary listing the last-modified revision
63
for all files in the project. This can be used similarly to how
64
``$Id$`` keywords are used in CVS-controlled files. The last
65
modified date can be determined by looking in the ``revisions``
66
map. This is also empty by default, and enabled only by ``--all``
67
or ``--include-file-revisions``.
70
Projects in other languages
71
---------------------------
73
Support for dumping version information in other languages is currently
74
in development. Please contact us on the mailing list about your
75
requirements in this area. (As of the Bazaar 1.0 release date, some patches
76
are available for other languages but are not yet merged into the core product.)
82
Most information about the contents of the project can be cheaply
83
determined by just reading the revision entry. However, it can be useful
84
to know if the working tree was completely up-to-date when it was
85
packaged, or if there was a local modification. By supplying either
86
``--all`` or ``--check-clean``, ``bzr`` will inspect the working tree, and
87
set the ``clean`` flag in ``version_info``, as well as set entries in
88
``file_revisions`` as ``modified`` where appropriate.
91
vim: tw=74 ft=rst spell spelllang=en_us