Known nodejs bug[1] has proposed fix [2] applied directly here.

[1] https://github.com/nodejs/node/issues/9137
[2] https://github.com/riedonetworks/meta-nodejs/commits/dora/recipes/nodejs/files/0001-fix-execvp-printf-argument-list-too-long.patch

It already happened that the first tests of the suite failed
because the MySQL server was not fully started:

    OperationalError: (2002, 'Can\'t connect to local MySQL server through socket \'.../var/run/mariadb.sock\' (2 "No such file or directory")')

  We require 8 spaces after the second line for adjust the layout at the generated file.

perl/bin/enc2xs can be a shell script that calls enc2xs.shebang so we
cannot call it explicitly with perl like "/path/to/perl
/path/to/enc2xs" but simply calling "/path/to/enc2xs" is enough and
safe.

  Make the integration with erp5testnode separeted from original SR.
  Optimise KVM resilient tests by downloading the test image on the software release site,
  without change the original SR. (This will sabe internet and speed up result).

also drop non-existing '--with-nm' option.

  The image still way too big but it is better the whole image

  This is just cosmetics.

  This fixes bugs on the order of parts and duplicated sections introduced on:
    8d28b7e0
    d3df3b6e

  Simple Don't repeat yourself.

  This change allow us simplify accross the instances usage of logrotate

  If the password file is overwriten by a third part application,
  an wrong n can be added to the file. The change on this recipe
  allow us automatically fix this miss behaviour.

component/autoconf: call autom4te during build with SlapOS perl explicitly to avoid shebang line length limit.

  as buildout.hash.cfg uses templates/.. filename has to be defined here again.

  The testsuite folder is used to change default software type while test slaprunner/kvm as
  currently the erp5testnode don't support diferent software type than default.

  Probably this folder will be removed or re-purposed in future.

background: firefox 51 outputs non-ASCII character when it is terminated and current erp5.util cannot recognize well if the test finishes.
this commit is a workaround for this issue, so that we can use firefox 51 without touching ERP5TypeFunctionalTestCase, that is important to test old ERP5 revision.

also quote arguments.

This is a follow-up of commit 8f032e6d:
Bison is only required when building from the repository.