When we have a section to generate a python interpreter with eggs built
in, don't name this `extra-eggs` because the meaning is not clear.

This section installs slapos.toolbox eggs with dependencies and install
scripts

Despite the name, this section was inherited from monitor, but now that
we fixed monitor to prefix the sections, this section is no longer
extended from monitor, but defined in softwares

This prevent naming conflicts in softwares extending and is cleaner.

Also other cleanups:
 - install an interpreter with a prefix, for similar reason
 - list monitor scripts explicitly, so that we don't have collisions
   with other sections installing same eggs (eg. slapos.core)
 - use ${buildout:bin-directory} instead of guessing it

This section installs a slapos command with network cache enabled, for
softwares using an embedded slapos.

Only install required eggs, drop unused [testnode] section

this section is supposed to install slapos.cookbook, the egg with
recipe at this point slapos.libnetworkcache should be already available.

* use strings for options, not `sets` which requires to use the `'!py!'` syntax and only works on a patched buildout
* supports regenerating config, like when for example IP change
* Removes the backup part of the recipe, which we don't use and looks buggy.
* fix python3 support

See merge request !727

This should fix this random failure with tests:

    ======================================================================
    FAIL: test_influxdb_api (test.TestInfluxDb)
    ----------------------------------------------------------------------
    Traceback (most recent call last):
      File "parts/slapos-repository/software/grafana/test/test.py", line 126, in test_influxdb_api
        [connection_params['influxdb-database']], result['series'][0]['values'])
    AssertionError: ['telegraf'] not found in [[u'_internal']]

This script everything required to release slapos.cookbook, and verbose additional information to
the user review and push the changes.

This script automatically slapos.cookbook version on update stack/slapos.cfg also, if you want only
release the EGG w/o using it, you can call it using:

 EGG_ONLY=Y bash release-cookbook

else, call it only by 'bash release-cookbook'.

  This script should be invoked to release a new software release, it will use what is in 1.0 branch to create
  the tag, and it will verbose the follow information...

###################################################################
You are about to release a new version of SlapOS Software Release
Lastest release: 1.0.144
Next Release to be Tagged: 1.0.145
###################################################################
 Please review current tag and them push it:
 To review use git log 1.0.145

 To push into main repository:
 git push origin 1.0.145

Update Thiea to 1.0, described a bit on :
 https://dev.to/svenefftinge/theia-1-0-finally-a-good-browser-ide-3ok0

Add by default some extensions for python and buildout. Also request a frontend so that we can access over IPv4

See merge request !725

As we have runners with a section deployed using
collective.recipe.shelloutput, if collective.recipe.shelloutput isn't in
the SR folder anymore thisi section can't be uninstalled (as the
uninstall method is defined in the egg).

The output of buildout for this error was :

While:
  Installing.
  Uninstalling runner-sshkeys-publickey-fingerprint-shelloutput.
  Installing recipe collective.recipe.shelloutput.
  Getting distribution for 'collective.recipe.shelloutput'.
Error: We don't have a distribution for collective.recipe.shelloutput
and can't install one in offline (no-install) mode.
While:
  Installing switch_softwaretype.

The cause was f936ea2c

Starting from slapos.recipe.build@5e95d882 gitclone should have built-in support for submodules. Credit: Kirill.

The error was :

 Error: The following paths are already installed by other sections:
 {'/opt/slapgrid/4eb4146f38fc86ed2ad060217a1a95a6/bin/slapos-watchdog':
 'extra-eggs',
 '/opt/slapgrid/4eb4146f38fc86ed2ad060217a1a95a6/bin/networkcache-download':
 'slapos-cookbook',
 '/opt/slapgrid/4eb4146f38fc86ed2ad060217a1a95a6/bin/slapos':
 'extra-eggs',
 '/opt/slapgrid/4eb4146f38fc86ed2ad060217a1a95a6/bin/generate-signature-key':
 'slapos-cookbook',
 '/opt/slapgrid/4eb4146f38fc86ed2ad060217a1a95a6/bin/networkcache-upload':
 'slapos-cookbook'}

There was a typo and anyway it wouldn't have worked because of
slapos.buildout!11

This is not used, and probably buggy

Since the first version, this have been writing config files in binary
mode, but these are really text files.

If for example the ip changed, this recipe needs to re-generate
configuration files.

Use the first ipv6 to generate the URL

Mostly useful for components that are built with cmake.

c++ already exists. cmake searches for c++ in the same folder as it found cc.

Another part wrote to etc/service/frontend_apache, which resulted of
impossibility to start apache after instance is restarted.

This was relying on a slapos patch allowing to serialize sets, but
that was not useful, because we had to encode the sets ourselves in the
profiles.

The issue is that the upstream package has been bworked (it is not
a .tar.gz in reality), which explains why the md5sum changed).

The source code is also available on github, but with a 3rd md5sum.

This reverts commit 2f705697.

See merge request !723

See merge request !724

Since `buildout 2.7.1+slapos002`, we `Check that sections don't installed the same path`, so we need to adjust some profiles which were not respecting this rule.

This fixes the regression introduced by nexedi/slapos@bbd70f7d

See merge request !726

use another port so that we can run tests on test node, port 8080 is
already used by testnode.