There is a story for OpenSSL build to be broken for `make -j`. Gentoo-
and various other people proposed fixes, at least from 2008, but for
some reasons (patch does not work with BSD make, upstream forgot to
apply, etc) they are not applied to main codebase.

What we can do is to "cherry-pick" the patch from Gentoo to speed-up
OpenSSL build. On a typical 8-cores i7 node, with the following test
buildout:

    [buildout]
    extends =
      slapos/stack/slapos.cfg
      slapos/component/openssl/buildout.cfg

after full build

                    time (rm -rf parts/openssl && ./bin/buildout install openssl)

    MAKEFLAGS=-j1   1m48s
    MAKEFLAGS=-j8   0m53s

and the timing does not subtract time to e.g. download the package from
network, so the building speedup itself is even more.

/cc @kazuhiko

We'll soon need to apply/ship external patches for openssl with us, and
external patches and patches in general usually go in -p1 format.

Since patch-options is "global" - i.e. it affects all patches for
slapos.recipe.cmmi, this change is needed for us to keep
downloaded-from-somewhere patches as unmodified as possible.

/cc @kazuhiko

In 2d7e6179 (wendelin.core: Add part/recipe how to build it from git
repository) I've added wendelin.core-dev part, but forgot to set :egg
variable inside it.

Reviewed-by: Trust-me

Hello web

Hello up there.

While studying how SlapOS works, I've turned helloworld example into real web-service.

New helloworld software-release was tested ok:

    - inside webrunner, and
    - instantiating in "raw" slapos locally under slapproxy.

Please apply and thanks beforehand,
Kirill

See merge request !2

Quoting @jerome:

    @kirr, we usually extends component/git/buildout.cfg and use
    ${git:location}/bin/git instead of git, in case git is not always in the
    path, especially in webrunner.

also use our own libraries more.
clean up rpy2 component.

because nodejs does not compile in testnode in webrunner

It is probably better to stop using grunt

This reverts commit 27fd1355.

Let's merge and switch wendelin development to master.

For now we only add components which should be orthogonal to the rest
and cannot break things. Yet master is a focal point for joint effort
and people can try wendelin work-in-progress.
Acked-by: Ivan Tyagov <ivan@nexedi.com>

* wendelin:
  wendelin.core: Add part/recipe how to build it from git repository
  components: wendelin-core -> wendelin.core
  Add Ipython and pandas python libraries.
  Add wendelin-core.
  Add msgpack-python library.

There is now

    wendelin.core       and
    wendelin.core-dev

parts.

wendelin.core just installs released egg from pypi, and
wendelin.core-dev installs it from latest git version.

A reminder how to use wendelin.core-dev instead of wendelin.core:

if your buildout.cfg

    [buildout]
        # directly or indirectly
        extends = ..../wendelin.core/buildout.cfg

then at tails, do

    [buildout]
        parts -= wendelin.core
        parts += wendelin.core-dev

This way wendelin.core will be fetched from git repository.