Update passenger to 5.1.12

[jfqd]

Would it be possible to get passenger version 5.1.12 into 2017Q4? 5.0.6 is really outdated (March 31, 2015). btw: passenger is the main way to deploy ruby webapps.

[mamash]

Possibly, yes. It's been almost three years since since I last touched the packages, mainly because there has been very little interest, and upstream always makes changes that make it a real pain to package things up properly.

[jfqd]

I understand, but passenger is the main way to deploy ruby webapps :)

I did ips-packages it in the past for OmniOS: https://github.com/jfqd/omnios-userland/blob/151014/build/ruby-2.2-passenger5/build.sh

And 5.0.30 has a CVE: https://www.cvedetails.com/cve/CVE-2016-10345/

[mamash]

I think I got it. Let me clean it up, provide nginx integration and commit to main pkgsrc tree this time.

[jfqd]

@mamash Wow, that would be cool!

[jfqd]

@mamash do you have a repo somewhere I can pull to test the build?

[mamash]

It's in trunk pkgsrc already... ;)

https://github.com/NetBSD/pkgsrc/tree/trunk/www/passenger

[jfqd]

Thx a lot! I was able to build ruby23-passenger and ap24-ruby23-passenger on SmartOS 2017Q4.

But how can I build ruby22-passenger and ap24-ruby22-passenger? Are there any Flags I need to set for bmake?

[mamash]

Yes, just set RUBY_VERSION_DEFAULT=24 in mk.conf or when calling bmake (e.g. bmake RUBY_VERSION_DEFAULT=24 install).

[jfqd]

There are always things to learn :) Do I need the RUBY_VERSION_DEFAULT flag only for install?

Would be cool to build and then run:

bmake RUBY_VERSION_DEFAULT=22 install
bmake RUBY_VERSION_DEFAULT=23 install
bmake RUBY_VERSION_DEFAULT=24 install

[mamash]

No, of course not. That's assuming you start with 'bmake clean'. You need the version set in order for the right dependencies to get installed etc.

[jfqd]

I did build the ruby22 versions and tested it with success on a SmartOS 2017Q4 vm.

[mamash]

I'm backporting this to 2017Q4. Just hit another issue with an ambiguous reference to a symbol, so it will show up with the next rebuild.