build: Add VARIATION variable to binary target

[stefanmb]

If the VARIATION variable is present, then "make binary" will produce archives named node-$(FULLVERSION)-$(PLATFORM)-$(ARCH)-$(VARIATION).

This capability is useful when building variations of Node.js for the same platform/architecture. For example, when building x64 Linux with FIPS compliant crypto provider, it is useful to have a "-fips" suffix to easily identify this functionality without having to examine the contents.

Contrast: node-v6.0.0-linux-x64.tar.gz vs node-v6.0.0-linux-x64-variation.tar.gz

[rvagg]

not a bad idea, I think, /cc @nodejs/build

[jbergstroem]

Sure, see no issue with it either.

[stefanmb]

@mhdawson Does this look okay to you? Thanks!

[mhdawson]

lgtm

[stefanmb]

@jasnell In the absence of @mhdawson would you be okay with merging this? Thanks!

[jbergstroem]

I can land it -- @rvagg LGTY?

[jasnell]

Sorry, just saw this, yeah LGTM!
On Jan 20, 2016 3:36 PM, "Stefan Budeanu" [email protected] wrote:

@jasnell https://github.com/jasnell In the absence of @mhdawson
https://github.com/mhdawson would you be okay with merging this? Thanks!

—
Reply to this email directly or view it on GitHub
#4631 (comment).

[rvagg]

lgtm pending https://ci.nodejs.org/job/node-test-pull-request/1338/

We also need to pay attention to the next nightly that comes out of this when landed to make sure it's working OK.

[jbergstroem]

arm fails seem unrelated. Merging.

[jbergstroem]

Landed in bf12379.

[jasnell]

marking this one as do not land in v4.x. It would likely be ok to land but given the change to the filename it could potentially break tooling. If anyone feels lts is appropriate, however, lemme know :-)