Global, local and module not rely on version classes to work anymore

[rafaelfranca]

We could remove all the version class but the aliases. WDYT?

[blackjid]

You did that for the ruby module right? mmm, those version classes are a maintenance nightmare.. :) I think they can be removed....

Probabley in the readme we should change the

# install any arbitrary nodejs version
nodejs { 'v0.10.1': }

with

# install any arbitrary nodejs version
nodejs::version { 'v0.10.1': }

[rafaelfranca]

Yes. we need to update the readme too.

[blackjid]

something like that?

[rafaelfranca]

One more step we can do is make possible to configure these aliases versions using hiera so we don't need to add a new class if node 0.12 is released.

[blackjid]

That will require more work/time. :) I have never quite understood how hiera works. But may be is a good time to learn... I will look to the ruby module.

[blackjid]

@rafaelfranca ok, finally. The ruby module was a lot of help..

[blackjid]

@rafaelfranca A few more fixes, to set if will install compiling from source or not... I thinks that this should be it... It is working for me at least... :)

[blackjid]

@rafaelfranca don't forget this PR, please :)

[rafaelfranca]

Seems good. Just need a rebase. Could you take a look?

[blackjid]

Rebased, do you want me to squash it into few commits?

[blackjid]

@rafaelfranca ?? have you had any time?

[rafaelfranca]

I didn't saw you rebase. Thanks. I'll release later when I test it locally

[blackjid]

:+1:

[indirect]

Does this add support for setting nodejs::global using Hiera? If it does, can you add it to the readme? If not, 😭

[blackjid]

nop, it doesn't. I mainly based my work on the boxen/puppet-ruby module, and that one doesn't support global using hiera either... sorry

[rafaelfranca]

Released as https://github.com/boxen/puppet-nodejs/releases/tag/4.0.0