Support the popular pip editable installation mode.
To work-around a problem in setuptools' develop target, generalize
'install_dir' to say all packages are in 'src' (for more info, see:
https://github.com/pypa/pip/issues/126).
Remove pre-generated bin/tito-dev script.
createrepo_c is a faster and more correct implementation of
generating rpm repositories, used by Fedora, openSUSE, and Mageia
for creating official distro repositories. It is also used by COPR
for creating repositories for packages built through its system.
Alas, python3 doesn't have the cmp() function.
Support both python2 and python3 for comparisons using tip from
https://docs.python.org/3.0/whatsnew/3.0.html#ordering-comparisons
Avoids TB on python3:
======================================================================
ERROR: test_compare_version (unit.common-tests.ExtractBugzillasTest)
----------------------------------------------------------------------
Traceback (most recent call last):
File "/home/sandbox/test/unit/common-tests.py", line 224, in test_compare_version
self.assertEquals(0, compare_version("1", "1"))
File "/home/sandbox/src/tito/common.py", line 689, in compare_version
return cmp(normalize(version1), normalize(version2))
NameError: global name 'cmp' is not defined
Add URL of upstream tito repo to HACKING, then
symlink HACKING as README.md in each Dockerfile dir.
Why?
If a README.md exists in same dir as Dockerfile (incl. symlink),
and it's set up as a
[trusted build](https://index.docker.io/help/docs/#trustedbuilds),
then index.docker.io automatically shows the readme on the info
page of the trusted build.
Exceptions are now compatible with both python 2.4 and 3.3,
and we have unit tests to detect regressions.
The syntax for capturing exceptions changed in python 3, but
we need to continue supporting python 2.4 syntax since many
people use tito on RHEL 5, which has python 2.4.
http://docs.python.org/dev/howto/pyporting.html#capturing-the-currently-raised-exception
* If a dev adds an editorconfig plugin to their editor,
automatically configure their editor for code style.
* Specify 4-space softtabs so new code will be compatible
with Python 3.
* Put the same settings in .gitattributes so git diff
highlights whitespace errors.
