Node package for Solaris 10 (x86)

[Peter Tribble]

For those Solaris 10 (x86) users who don't want to go the trouble of
building Node themselves, I've put together a package (including
openssl, cURL, and npm). I had got this all lined up for v0.4.8 and
then v0.4.9 came out. Details and package available here:

http://www.petertribble.co.uk/Solaris/node.html

--
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/

[George Bailey]

If you provided a package that did not include openssl built in, I
would appreciate it. I guess you would exclude cURL while including
npm.

Your install is required to reside in /opt/Node. I would like an
install that resides in a directory I choose. I am able to extract
your pkg using a simple pkgtrans command (see
http://serverfault.com/questions/287469/extract-files-out-of-solaris-pkg-file-without-installing/287472#287472),
but it does not work.

# cd /our_own_directory/our_own_prefix_specific_for_this_package
# ./root/opt/Node/bin/node
ld.so.1: node: fatal: libssl.so.1.0.0: open failed: No such file or
directory
#

If a symbolic link is added so /opt/Node points to /our_own_directory/
our_own_prefix_specific_for_this_package/root/opt/Node, the problem
goes away.

However, this is not permitted in our environment. But I know for a
fact that node can be built without openssl built in, and be portable
to any directory.

[Peter Tribble]

On Wed, Jul 6, 2011 at 2:23 PM, George Bailey <cjav...@gmail.com> wrote:
> If you provided a package that did not include openssl built in, I
> would appreciate it. I guess you would exclude cURL while including
> npm.

I've built a new node package for Solaris 10, available from:

http://www.petertribble.co.uk/Solaris/node.html

Updated for Node 0.4.10. This uses the system openssl, so that problem
goes away.

It still includes a copy of curl, which npm needs. If you just use the
files out of the
package then you can get rid of the included curl (assuming you have one of your
own).

Or you could set LD_LIBRARY_PATH, of course - situations like this are what it's
good for.

[Oleg Efimov (Sannis)]

You can extract a part of npm's install.sh to get the URL of full npm source code and include it to your package. It will allow to exnclude cURL from the package.
Npm simple installs from source with command like this:
#>npm_config_prefix=/opt/npm node cli.js install -g

[Peter Tribble]

On Fri, Feb 8, 2013 at 6:10 PM, Will Arroyo <warroyo...@gmail.com> wrote:
> I know this is an old thread but I want to use your package for solaris 10.
> Only thing is I want to install it in my home directory not opt/node. how
> can this be done?

You can extract the files out of a package with pkgtrans, the only
bit this will miss is any symbolic or hard links.

Something like this ought to work:

bunzip2 TRIBnode-0.8.19.0.pkg.bz2
pkgtrans TRIBnode-0.8.19.0.pkg .
mv TRIBnode/root/opt/Node .

you'll need to set LD_LIBRARY_PATH (one day I'll get around
to fixing this because it shouldn't really be necessary)

env LD_LIBRARY_PATH=Node/lib PATH=Node/bin:$PATH node ...

and if you want npm to work there are a few more symlinks

cd Node/lib
ln -s libcurl.so.4.2.0 libcurl.so.4
ln -s libcurl.so.4.2.0 libcurl.so
cd ../bin
ln -s /usr/sfw/bin/gmake make
ln -s ../lib/node_modules/npm/bin/npm-cli.js*
ln -s /usr/sfw/bin/gtar tar

[Will Arroyo]

Wow thanks for the fast response! I also already have curl installed, so in order to use my own curl would I just change those sym links?

[Peter Tribble]

On Fri, Feb 8, 2013 at 6:38 PM, Will Arroyo <warroyo...@gmail.com> wrote:
> Wow thanks for the fast response! I also already have curl installed, so in
> order to use my own curl would I just change those sym links?

No, if you arrange it so that it finds your curl first, then you'll
be fine. You could then just delete the curl I ship (which is just
a convenience for people who don't have it already). (Ditto the
symlinks for tar and make - I think npm expects the gnu versions
of tar and make.)

[Will Arroyo]

thank you for the help! I have got node running but i am having trouble with npm...all i see in the bin directory is a npm-cli.js file. is this suppose to be in my path?

[Peter Tribble]

On Fri, Feb 8, 2013 at 9:36 PM, Will Arroyo <warroyo...@gmail.com> wrote:
>
> thank you for the help! I have got node running but i am having trouble with
> npm...all i see in the bin directory is a npm-cli.js file. is this suppose
> to be in my path?

Oops (I didn't say I had thoroughly tested it). What I should have written was

cd bin
ln -s ../lib/node_modules/npm/bin/npm-cli.js npm

so that npm is a symlink to that script. You'll probably have to edit
that as well, so it's got the correct path to the node binary in it.

> --
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nod...@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+un...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "nodejs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to nodejs+un...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

[Will Arroyo]

Thanks again, I actually just figured it out right before your response. thanks for doing all the dirty work compiling it! its working great.