* Include `avocado.module` inside setup.py.
* Check if htmlresult plugin is installed from the import,
  to set the HTML result feature on or off.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

Introduce a new command line application that is designed to interact
with avocado-server.

Changes from v1:
* Fixed reference in the docstrings to arcli (from arc)
* Release number bump on spec file
* Add missing avocado.restclient.cli.actions module to setup.py
Signed-off-by: NCleber Rosa <crosa@redhat.com>

An essential part of a client interacting with avocado-server is to handle
the reponse of a request. The most common type of response type is a
results reponse, when one performs a GET to a resource "root" path and
and expects to return a list of resources.

To make that more pythonic, this commit introduces a ResultResponse class
that accepts the JSON response data and checks for completeness. If
results response fails to comply with the required data members, meaningful
exceptions will be raised.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This way, we fix a bug of avocado unable to list tests
from its own tree (it'll try to import them and then
fail due to recursively trying to import the already
loaded avocado modules).
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Minor improvement to the initial description in the man page
and update links to point to the (new) project page everywhere.
Signed-off-by: NAdemar de Souza Reis Jr <areis@redhat.com>

Whatever is in the system wide settings can be later
overriden by users. Also, change the settings.config_path
attribute to settings.config_paths, and change it to
a list. This way users can see the order in which their
config files are parsed. Also, Introduce a system wide conf.d
directory, that is supposed to ship config files for avocado
plugins. The order for config parsing is:

 * System wide avocado config (/etc/avocado/avocado.conf)
 * System wide avocado plugins config (/etc/avocado/conf.d/*.conf)
 * Local config for the user running avocado (~/.config/avocado/avocado.conf)
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

As discussed in the Trello card

https://trello.com/c/WsDMg7RP/161-initial-support-for-avocado-config-files-server-and-client

Move settings.ini to avocado.conf. The basic idea is
that the name is more intuitive.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Include all examples/wrappers/*.sh scripts when building
the `avocado-examples` package. The scripts will live under
`/usr/share/avocado/wrappers` when installed.
Signed-off-by: NRudá Moura <rmoura@redhat.com>

setuptools is not a standard module and makes things
unpredictable and forces us to push MANIFEST.in to
include more files so the binary distributions get
filled appropriately. In a retrospect, it was a bad
idea. Let's revert it.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Making justice to all our contributors, change this
silly instance of myself as the author of the whole
thing. Sorry about that.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Use setuptools's option install_requires, to signal
the dependencies avocado requires for full functionality.
Important for publishing avocado in PyPi [1].

[1] https://pypi.python.org/pypiSigned-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Package plugin resource files, as they're necessary to
the given plugin's functionality. Update MANIFEST.in
with the new data dir.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Without it, setup.py is interpreted as a bash script.

This page is intended as a basic offline aid for new users of avocado.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The use of virtual environments is a very useful feature
for developers and helps us to sanity check code instalability.
However, we were not able to use it because the data file
install has to be different for virt env and for regular
system wide install (RPMs).

This patch makes avocado aware of the execution mode,
and sets the install process so that it works differently
(and fine) for both normal install and virtenv install.

Additionally, this fixes a bug I introduced on installing
test files, that broke the avocado rpms.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

The tests dir layout has changed, update setup accordingly.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NCleber Rosa <crosa@redhat.com>

I was stupid enough to have a typo in URL (see previous commit).
Signed-off-by: NCleber Rosa <crosa@redhat.com>

While we don't have a proper homepage, point to the avocado repo.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

I went through all python files in avocado code, and
some changes were made:

* Files entirely written by the current avocado dev
team were changed to be GPL v2+
* Files with a significant portion of code derived
from autotest remain GPL v2 strict, and original
authorship was re-established
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Use the new inspektor functionality (with a few manual
tweaks later) to add copyright headers into each avocado
file.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Another step in making avocado to run system wide
(and provide distro packages).
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Let's simplify the program namespace. No need to add
nesting for this particular lib.
Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NRuda Moura <rmoura@redhat.com>

Signed-off-by: NRuda Moura <rmoura@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>

Signed-off-by: NLucas Meneghel Rodrigues <lmr@redhat.com>