So there are no clases in history of RPM releases.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

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

This builds a new sub package for this new optional plugin.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

PICT is a free software (MIT licensed) tool that implements
combinatorial testing.  Information about it can be found here:

   https://github.com/Microsoft/pict/

This is a very simple, but functional varianter implementation.  It
performs the basic tasks of creating variants and making parameters
accessible to tests.  To test this version, it's recommended to
download PICT, build it (it only takes a C compiler such as GCC or
clang and make) and put it in a location included in your PATH (or use
`--pict-binary`).

To list the variants generated with the default order (2, that is,
do a pairwise idenpendent combinatorial testing):

 $ avocado variants --pict-parameter-file=examples/params.pict
 Pict Variants (11):
 Variant amd-scsi-rtl8139-windows-rhel6-acff:    /run
 ...
 Variant amd-ide-e1000-linux-rhel6-eb43:    /run

To list the variants generated with a 3-way combination:

 $ avocado variants --pict-parameter-file=examples/params.pict \
   --pict-order-of-combinations=3

 Pict Variants (28):
 Variant intel-ide-virtio-windows-rhel7-aea5:    /run
 ...
 Variant intel-scsi-e1000-linux-rhel7-9f61:    /run

It's also possible to run tests with variants generated by the same
command line switches.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

Let's also package and build the recently introduced golang plugin.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

There's a problem with the current SPEC file in that it doesn't
exclude some of the files part of the "plugins-loader-yaml" package.

This would cause problems if that plugin package attempts to be
installed, causing conflicts because they're packaged on two packages.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This commit revomes flexmock from the various requirements file, from
the RPM SPEC file.  Starting here, it's officially no longer an
Avocado dependency.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

six is already a stevedore requirement, but since we'll now be
using it directly, it's a good idea to list it explicitly as
a dependency.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

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

A number of example files are not currently being packaged.  Let's
install and package them.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The current SPEC file changelog is getting really long.  I think
we can do better with a shorter version.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

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

The newly introduced YAML Loader plugin is currently hosted on the
same plugin (directory and module) as the varianter one.  While they
share a lot of code, they have different purposes.

Let's move the YAML loader into its own plugin, so that its
installation is also optional and the separation is clearer.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This change is already present on the downstream (Fedora/EPEL)
packages, and for some reason, was missing here.  It causes
the installation to be attempted by pip, which should never
be done during RPM builds.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

shortcommit is supposed to contain the 8 first characters instead of 7.
Signed-off-by: NAmador Pahim <apahim@redhat.com>

There's now python-aexpect packages on EL7, so we should
be using it.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

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

Currently the yaml_to_mux plugin is a core plugin without properly
defined requirements. Let's separate it to optional_plugins, define
dependencies and also build it separately in RPM.
Signed-off-by: NLukáš Doktor <ldoktor@redhat.com>

This change may help to quickly read the conditionals.  It's
already been applied on Fedora packages, so let's sync it here.

Also added here is some small comment section changes (mostly
capitalization), again to sync with downstream.

CC: Lukáš Doktor <ldoktor@redhat.com>
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

It's a fact that the Avocado package owns not only /var/lib/avocado/data,
but also /var/lib/avocado.  Let's fix that, so users doing something like:

 rpm -qf /var/lib/avocado

Would get the right information.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

This is basically to be explicit about selftest level run on check.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

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

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

This packages the newly introduced resultsdb optional plugin.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Avocado's "data_dir" has always been meant for readable **and** writable
content.

Right now, this is broken because the system wide default for
"base_dir" (data_dir's parent) is set to /usr/share/avocado, and
consequently, "data_dir" is set to /usr/share/avocado/data.

Let's use "/var/lib/avocado" for the "base_dir", and
"/var/lib/avocado/data" for the "data_dir".  Content intended to be
read-only, such as example tests and wrappers, are still set to
/usr/share/avocado.

This has been tested with Avocado-VT, making the result of system
wide content, such as test providers and downloadable files be
put under "/var/lib/avocado/data/avocado-vt".

Reference: https://trello.com/c/KU1DvSAzSigned-off-by: NCleber Rosa <crosa@redhat.com>

Commit 7a249b7c removed files that were intended to be packaged in the
optional plugin packages.  By doing so, they ended up in the main
package.

This fixes that issue, and puts both the directories with the
package and module name (which differ) into each optional plugin
package file listing.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

Downstream (Fedora and EPEL) RPM packages have had a different way
of building release (by default) and snapshot packages by editing
the SPEC file.

Let's sync with them, while also allowing snapshot packages to be
built from our usual `make rpm` command.  Release builds are still
supported with `make rpm-release`.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

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

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

Downstream file contains a conditional for the execution of
selftests.  Let's port that to the upstream SPEC file too.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

I have to say that having one requirement per line is really verbose,
but I have to admit that it makes diffs a lot easier to grasp.

Again, this syncs with the downstream SPEC file.
Signed-off-by: NCleber Rosa <crosa@redhat.com>

The first line says it all.  While this change wouldn't be really
required, it brings the SPEC file close to the Fedora/EPEL downstream
version.
Signed-off-by: NCleber Rosa <crosa@redhat.com>