~allenap/maas-test/resources-all-the-way-down

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
.. -*- mode: rst -*-

*********
maas-test
*********

A utility to test if a particular piece of hardware is compatible
with MAAS.

For more information see the `Launchpad project page`_.

.. _Launchpad project page: https://launchpad.net/maas-test


Setting up for development
--------------------------

To get maas-test running should be fairly easy, assuming you're on
Ubuntu 13.10 or later::

  bzr branch lp:maas-test
  cd maas-test
  make install-dependencies
  make build

The ``make install-dependencies`` step ensures that maas-test's
dependencies are installed as system packages, and will not later be
installed by pip.


Dependencies
------------

The policy is:

  * All production dependencies must be satisfied from system packages.

  * Development-only dependencies can be installed from PyPI.

That means that production dependencies need to go in ``packages.txt``
and development-only ones into ``requirements.txt``. The latter can be
maintained like so::

  bin/pip install some-new-dev-only-library
  bin/pip freeze --local > requirements.txt

Then **carefully** review the changes; libraries installed elsewhere on
the system can cause ``freeze --local`` to come up with radically
different answers to those on another machine.