The RPM repo is no longer accessible

[etiennep]

I had to revert to using wget to grab the distribution on CentOS because nodejs.tchol.org is no longer accessible.

[slippycheeze]

Hey. Thanks for this submission - having this third party service dependency, and their being down, is certainly a pain for us. We are starting to look at options - including this one - for working around the problem while we try to discover if the repository is going to come back.

Until we have an internal consensus on the best strategy I am going to keep this on the metaphorical back burner. It looks solid but it isn't the nicest way to get software installed, and we hope with the likely inclusion of NodeJS in Fedora 18, or the third party service recovering, that we can avoid this headache for our users.

[etiennep]

I agree with you. I just made the change to mimick what we already do here for some other packages until an RPM becomes available. It would be nice if it made it to that EPEL repo. Do you know if anybody is working on this?

[slippycheeze]

I agree with you. I just made the change to mimick what we already do here
for some other packages until an RPM becomes available. It would be nice if
it made it to that EPEL repo. Do you know if anybody is working on this?

Fedora 18 should contain NodeJS. All the third party packages needed
"substantial" work to get into either Fedora proper, or EPEL, because
the NodeJS people bundled libraries in violation of their policies.
Now that F18 has it, hopefully EPEL will backport it nicely - but it
isn't there yet.

[slippycheeze]

If a couple of people in the community report that http://patches.fedorapeople.org/oldnode/ works for them, I would switch over to it. It avoids the need to hand-roll the content here.

[razorsedge]

This should be fixed in #26 .

[brettporter]

Node is now in EPEL, and the versions in the "oldnode" repo stopped at 0.6. This makes manage_repo and "stable" a bit misleading.

I can think of a few alternatives here:

1. switch manage_repo to configure EPEL and remove nodejs-stable
2. rename manage_repo to manage_oldnode_repo (breaking)
3. drop support for manage_repo and have EPEL configured in some other way

Do any of those make sense?

[hunner]

I like that the wget solution will stand the test of time, as EPEL and other distros change their packaging with time: https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager , but I don't know if it's the right solution for such a popular and public piece of software (or this module).

I like having the package be the primary option (and many shops will build their own package for this and host out of their internal repos), but this module could use some heavy updating on that front.

I'm going to close this wget PR in the hopes that we can take advantage of the packaging that has happened since this was opened a year ago. If you would like to re-open this PR with nodejs::install::wget as an encapsulated alternative to package installation, I'd be open to that.