Rudder

This commit has been reverted, due to #2542 - CFEngine 3.3.x requires a too recent version of TokyoCabinet, and no longer supports BerkeleyDB. We don't have the time to handle this at the moment, so we're falling back to CFEngine 3.2.x - see #2583.

This may even be modified to to use CFEngine 3.4, which provides namespaces, a long awaited feature.

Actually, we want to upgrade to CFEngine 3.4

There is a problem for distribution that does not Tokyo Cabinet.
So, we will have to deals with them, and there is two way of dealing with that:

• create a package for that Database, and add it to our repos
  • problem: that means having to install several package for Rudder-agent, what we don't want
• compile (statically ?) Tokyo Cabinet and add it in our Rudder-agent Package
  • that means having different rudder-agent for different OS, but we already do that

François ARMAND wrote:

There is a problem for distribution that does not Tokyo Cabinet.
So, we will have to deals with them, and there is two way of dealing with that:

• create a package for that Database, and add it to our repos
  • problem: that means having to install several package for Rudder-agent, what we don't want
• compile (statically ?) Tokyo Cabinet and add it in our Rudder-agent Package
  • that means having different rudder-agent for different OS, but we already do that

• Consider that all supported OS have a package containing tokyocabinet with exceptions:
  • SLES 10, SLES 11 and RHEL 5 will need to embed a compiled tokyocabinet and we will be rid of this by if statements in the .spec files
  • Debian 5 will need to embed a compiled tokyocabinet but no equivalent of if statement exist in debian/rules. To get rid of this issue we have decided to use a patch to modify debian/{control,rules} of rudder-agent

All of this is made in #2542

This ticket has been addressed in version 2.6.0~beta1 of Rudder, which has just been released. Please see the changelog here: https://www.rudder-project.org/foswiki/System/Documentation:ChangeLog26.