Also, updating a part does not put it anymore at the end of the list of
installed parts. It was breaking uninstall dependencies.

Useful when recipes generate non-string values to be reused by other
recipes.

Add referred parts' hash strings in __buildout_signature__, that invokes rebuild of a part when one of its (recursive) dependencies are modified.

Also remove duplicates and sort entries in __buildout_signature__.

In SlapOS, bootstrap is called each time software release is invoked and
we do not want to delete develop-eggs directory.

This reverts commit 55d76b34.

--setuptools-version and --buildout-version options in bootstrap script still have the priority.

ref https://bugs.launchpad.net/zc.buildout/+bug/144228 .

Even though such configuration is wrong...

Currently only zc.recipe.egg:custom supports setting environment
variables, and zc.recipe.egg:develop does not.

My motivation for allowing setting environment in :develop is
wendelin.core

    https://lab.nexedi.cn/nexedi/slapos/blob/b5faab3b/component/wendelin.core/buildout.cfg

There we have [wendelin.core] part which installs released egg from
pypi, and [wendelin.core-dev] part which installs wendelin.core from
its latest git version via zc.recipe.egg:develop .

The problem is, wendelin.core for setup.py to work, needs git available,
and with slapos we usually don't have git available on base system, so
we build it by our own and do something like

    [wendelin.core-dev]
    recipe = zc.recipe.egg:develop
    environment = wendelin.core-dev-env

    [wendelin.core-dev-env]
    # wendelin.core-dev needs git to build
    PATH = ${git:location}/bin:%(PATH)s

and the problem is environment does not currently work for
zc.recipe.egg:develop, and thus git is not found -> build fails.

~~~~

In order to support environment in :develop, we just move environment
setting/restoring bits from Custom to Base, and provide Base.install() which
uses this bits. Custom & Develop .install() becomes ._install() which gets
hooked into Base.install() .

I've tested the patch only manually, because currently automated tests are
broken in a lot of places for slapos.buildout and zc.recipe.egg .

/cc @kazuhiko, @Tyagov

- Support on the fly patches in zc.recipe.egg by ``EGGNAME-patches``,
  ``EGGNAME-patch-options``, ``EGGNAME-patch-binary`` (or
  ``patch-binary``) and ``EGGNAME-patch-revision`` options.

- Support on the fly patches in zc.recipe.egg:custom by ``patches``,
  ``patch-options``, ``patch-binary`` and ``patch-revision`` options.
  (options ``EGGNAME-*`` are also supported as well).

In order to have as canonical as possible paths, chomp ../ from filenames and
recalculate base.

[ci skip]

distutils scripts for develoment eggs are also installed

-x means "do not install scripts" and we're doing that now.
So the test needed to be adjusted.

Upgraded version pins

This only impacts testing.
Note that
VersionConflict: (zc.recipe.testrunner 2.0.0 (/Users/reinout/.buildout/eggs/zc.recipe.testrunner-2.0.0-py2.7.egg), Requirement.parse('zc.recipe.testrunner==1.3.0'))
means you have to remove .installed.cfg. Pinning a recipe version in a 'recipe=' line isn't handy.

fix for win32 '#!"python"' vs '#!python' shebang

A pip issue prevents installation of wheels with ``.egg`` in their name...

[ci skip]

[ci skip]

Wheel support also for zc.recipe.egg