Patch for raspberry pi 2 build

This will allow us to patch deb packager for building Raspberry Pi 2 packages on Scaleway servers.

More info on this can be found at https://github.com/chef/omnibus/issues/352. PR for improving omnibus is here https://github.com/chef/omnibus/pull/474. However, in our specific use case this won't be enough as OS we are using to build the package is Debian. The added patch file is applied at build time.

Edit to the makefile is also due to building on Debian, I want a clear separation between debian packages and packages build for RPI2.

Packages built this way were tested on Raspberry Pi 2 with Raspbian OS.

cc @jacobvosmaer

How is the patch applied?

Instead of patching the 'omnibus' gem, maybe we could just fork it?

@jacobvosmaer Check the build script at https://ci.gitlab.org/projects/55/jobs . I really find it an overkill to fork the omnibus gem, we then need to constantly maintain it. I also do not know where to document this for anyone interested, perhaps doc/build.md ?

OK so we have a custom, private build script for raspberry pi not tracked by version control. And we patch a gem in our own bundle before running 'make'. And we don't know where to document all this. A fork might be a simpler, more transparent solution. :) Explain in the README why we forked, update the Gemfile to pull the fork from github, done.

I know it is no fun to baby-sit a forked gem but it seems like a more 'standard'/less surprising solution in this case.

Fiiine, that is exactly what I wanted to avoid :) But you are right, even with something not so crucial we should do it properly.

Status changed to closed