This recipe will be used to generate promise in etc/plugin dir. It solve the problem of promise eggs
dependencies and allow to set custom parameter to use in promise.

The generated script will looks like:

    import sys
    sys.path[0:0] = [
      ...
    ]

    extra_config_dict = {
      'KEY': 'VALUE'
    }

    CONTENT

CONTENT is a python code, the expected content looks like:

    from namespace.module import RunPromise

then the promise section in buildout will be something like:

    [my-promise]
    recipe = slapos.cookbook:promise.plugin
    eggs =
      NAME
      ...
    output = OUTPUT
    content =
      from namespace.module import RunPromise

    config-KEY = VALUE

This function factorize the code to instanciate a recipe in a fake
buildout.
The new feature is that if running in a buildout directory, the recipe
will reuse the eggs from this buildout instead of trying to install eggs
again.

we now use slapos.cookbook:wrapper instead

We are supposed to have valid certificates and if really needed,
slapos.recipe.build:gitclone can ignore it.

reviewed on !300

thx @jerome

Current version of wendelin.core is limited in that there's no cooperation
in memory allocation between several processes sharing the same /dev/shm.
Over time, the distribution of memory among processes becomes more and more
inequal until some of them get killed due to allocation failure.

This is a temporary solution that relies on user namespaces.

This moves most of the wrapper recipe to GenericBaseRecipe so that
createWrapper automatically switches to Python scripts for complex cases.

Recipes should not use slapos.recipe.librecipe.execute.generic_exec directly
anymore.

It was used in only 2 places and createPythonScript has no equivalent
(maybe reusing 'initialization' from easy_install would produce something
readable enough). For the moment, let's drop this parameter, so that
createWrapper can switch to Python wrappers for complex cases.

There was an inconsistency between the 2 ways of creating executable wrappers:
- createWrapper: parameters-extra defaults to False
- slapos.recipe.librecipe.execute.generic_exec: no option, enabled

An option for that is not worth the effort.
Let's always enable even if it's meaningless.

/software/ and /stack/ will be cleaned up once a new version of this egg
is released.

The workaround for shebang size limitation is removed because it's redundant
with what is done by zc.buildout.easy_install and slapos.recipe.cmmi. This also
fix the issue that a process has a bad name even when the workaround is useless.

kumofs is even abandonned software.

getWorkingSet() is slow and it is not always needed. So, it is better not to call it in __init__.

Revert "slapos/recipe/librecipe/generic.py: GenericBaseRecipe's _ws is a lazy attribute now."

This reverts commit 281d3774.

getWorkingSet() is slow and it is not always needed. So, it is better not to call it in __init__.

In the particular case of PATH, '' is the same as '.',
which is a bad idea from a security point of view.

inotifyx does not support Python 3.

Test will fail if /tmp/instance_test_resourcefile already exists

All tests from `slapos.test.recipe` module were executed twice since f8de4cc4  when running as `python setup.py test`


`python setup.py test --test-suite slapos.test.test_recipe.additional_tests` still runs only tests for recipes and `python setup.py test` runs tests for recipe and static tests for software releases (for now json schema).

@rafael @katomaso 

/reviewed-on !234

Since erp5@6c6b77a0, this is now a safe
operation, in that a mistake while moving databases won't result in a loss of
the catalog if the zodb is empty.

This new implementation relies on
erp5@6bb4c56e, which means that zopes
decide on their own to create the site at startup if there's none, and the
'erp5-bootstrap' service is removed from the root partition.

/reviewed-on !217

See !196

The whole code is small enough and having the template
in a separate file only made editing more annoying.

Add functionality to wrapper to ask for an exclusive CPU core.

/reviewed-on !184

/reviewed-on !166

Buildout commit in discussion:  slapos.buildout@43839169

/reviewed-on !176