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
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
|
Developer's Guide
=================
Changelog
---------
.. toctree::
:maxdepth: 1
changelog
Bug reports and feature requests
--------------------------------
- `Submit a bug report <https://github.com/vcstools/rosinstall/issues>`_
Developer Setup
---------------
The rosinstall source can be downloaded using Mercurial::
$ git clone https://github.com/vcstools/rosinstall.git
You will also need vcstools, which you can either install using pip or download using::
$ git clone https://github.com/vcstools/vcstools.git
$ cd vcstools
$ python develop
To work on the bash completion, there is a separate repository::
$ git clone https://github.com/vcstools/rosinstall_tab_completion.git
That one does not contain python code.
rosinstall uses `setuptools <http://pypi.python.org/pypi/setuptools>`_,
which you will need to download and install in order to run the
packaging. We use setuptools instead of distutils in order to be able
use ``setup()`` keys like ``install_requires``.
Configure your environment:
$ cd rosinstall
$ python develop
Testing
-------
Install test dependencies
::
$ pip install nose
$ pip install mock
rosinstall uses `Python nose
<http://readthedocs.org/docs/nose/en/latest/>`_ for testing, which is
a fairly simple and straightforward test framework. The rosinstall
mainly use :mod:`unittest` to construct test fixtures, but with nose
you can also just write a function that starts with the name ``test``
and use normal ``assert`` statements.
rosinstall also uses `mock <http://www.voidspace.org.uk/python/mock/>`_
to create mocks for testing.
You can run the tests, including coverage, as follows:
::
$ cd rosinstall
$ make test
Documentation
-------------
Sphinx is used to provide API documentation for rosinstall. The documents
are stored in the ``doc`` sub-directory.
You can build the docs as follows:
::
$ cd rosinstall/doc
$ make html
.. _inofficial-format:
Inofficial file format
----------------------
The willow garage build system relies on these two extensions to the rosinstall file format.
Basic element types include 'tar', and meta properties can be attached.
Example::
- svn:
local-name: rosorg
meta:
repo-name: ros-docs
uri: https://code.ros.org/svn/ros/stacks/rosorg/trunk
- tar:
local-name: foo.tar.bvz2
version: foo-1.2.0
The meta element has no further semantics to rosinstall, it is just passed through.
The tar element is an unsupported but required feature of vcstools, with the peculiar
semantics that 'version' must refer to a folder inside the tar root.
|
