Set pre-release version

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
run-setup: easier-to-type wrapper for "python setup.py"

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
setup.py: fix download_url + parametrize both urls

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
Update the package description, point out use as a lib

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
plugin_registry: fix overly keen (nested) plugin discovery

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
format: during "walk", also skip files starting with a dot

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
plugin_registry: also this discovery skips '[.]*' files

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
Make run-dev central point for local use (e.g., test run)

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
filters/cluster: fix relative imports (silent malfunction)

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
setup.py: include default.py.in into source distribution

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
setup.py: smarter self-discovery (how am I called as package)

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
setup.cfg: nano editor as a lowest common denominator

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
MANIFEST: capture ccs-flatten source for sure

Previously it used to (mysteriously) depend on whether "setup.py build"
was called explicitly prior to "setup.py sdist".  Because of this
strangness, official 0.1.1 release is missing these sources :-/

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
run-dev: better way of dealing with various contexts of use

Actually a more robust variant of what setup.py uses.

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
setup.cfg: install ccs_flatten binary rather under dedicated dir

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
ccs-flatten/resrules: convenient "this dir": metadata only

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
filters/ccs2ccsflat+ccs_flatten: nothing to do -> return orig. dump

This way, we do not have to bother with stdin and/or magic file
descriptors.  At the cons' side, the equality check is little bit
complicated with a need to normalize both before-after variants,
but this only affects tests anyway (that are accommodating this
change as of now).

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
Adjust a way to operate in "development" mode wrt. run-dev

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
tests: add __init__.py to allow custom test picking

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>
run-tests: less verbose, more likely to work with set -e

Signed-off-by: Jan Pokorný <jpokorny@redhat.com>