Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation says CentOS 5 is supported using package manager but it is not true #190

Closed
logoff opened this issue Dec 4, 2015 · 5 comments

Comments

@logoff
Copy link

logoff commented Dec 4, 2015

This documentation page and this page say that CentOS 5 64 bits is supported, but when I follow the script in my CentOS 5 VM this is the result:

## Confirming "el5-x86_64" is supported...

+ curl -sLf -o /dev/null 'https://rpm.nodesource.com/pub_0.10/el/5/x86_64/nodesource-release-el5-1.noarch.rpm'

## Your distribution, identified as "centos-release-5-6.el5.centos.1", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support
@helioricardo
Copy link

Same here with "centos-release-5-11.el5.centos"

Your distribution, identified as "centos-release-5-11.el5.centos", is not currently supported, please contact NodeSource at https://github.com/nodesource/distributions/issues if you think this is incorrect or would like your distribution to be considered for support.

@geoff-maddock
Copy link

Any explanation as to why it is not supported? I'm experiencing the same issue as the OP.

@chrislea
Copy link
Contributor

chrislea commented Mar 2, 2016

EL5 is only currently supported for Node 0.10.x, so if you are trying to install a newer version that would explain why you are seeing the unsupported message. The reason is that the C++ compiler and the version of python that ship on EL5 are too old to build modern Node releases. I'm looking in to being able to build it using other toolchains, but it's not currently very high on the TODO list.

@logoff
Copy link
Author

logoff commented Mar 3, 2016

Thank you for the comment @chrislea. Maybe the proper solution is adding this limitation in the official documentation to avoid confusion.

@retrohacker
Copy link
Contributor

@logoff, great suggestion. I've added this to the new FAQ and linked back to this issue.

It will land in #308

For now, as @chrislea said, adding support for EL5 for newer versions of Node.js is something we are considering. Closing this for now. We will revisit this after the migration to the new infrastructure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants