DescriptionPhusion Passenger is an Nginx module, which makes deploying Ruby
and Ruby on Rails applications on Nginx a breeze. It follows the
usual Ruby on Rails conventions, such as "Don't-Repeat-Yourself"
and ease of setup, while at the same time providing enough
flexibility.

Log message:
Update to passenger 3.0.7
Ignore EINVAL from sigaltstack, seems to be what ruby itself does in 1.9
committing on behalf of jeremy@, who did all the work,
tested on i386 and tested packaging on amd64. All so I can commit a
simple nginx update... THANKS.
ok jasper

Log message:
Update to passenger 3.0.7
Ignore EINVAL from sigaltstack, seems to be what ruby itself does in 1.9
committing on behalf of jeremy@, who did all the work,
tested on i386 and tested packaging on amd64. All so I can commit a
simple nginx update... THANKS.
ok jasper

Log message:
Update to passenger 3.0.7
Ignore EINVAL from sigaltstack, seems to be what ruby itself does in 1.9
committing on behalf of jeremy@, who did all the work,
tested on i386 and tested packaging on amd64. All so I can commit a
simple nginx update... THANKS.
ok jasper

Log message:
Update to passenger 3.0.7
Ignore EINVAL from sigaltstack, seems to be what ruby itself does in 1.9
committing on behalf of jeremy@, who did all the work,
tested on i386 and tested packaging on amd64. All so I can commit a
simple nginx update... THANKS.
ok jasper

Log message:
Update to passenger 3.0.7
Ignore EINVAL from sigaltstack, seems to be what ruby itself does in 1.9
committing on behalf of jeremy@, who did all the work,
tested on i386 and tested packaging on amd64. All so I can commit a
simple nginx update... THANKS.
ok jasper

Log message:
Update to passenger 3.0.7
Ignore EINVAL from sigaltstack, seems to be what ruby itself does in 1.9
committing on behalf of jeremy@, who did all the work,
tested on i386 and tested packaging on amd64. All so I can commit a
simple nginx update... THANKS.
ok jasper

Log message:
Update to passenger 3.0.7
Ignore EINVAL from sigaltstack, seems to be what ruby itself does in 1.9
committing on behalf of jeremy@, who did all the work,
tested on i386 and tested packaging on amd64. All so I can commit a
simple nginx update... THANKS.
ok jasper

Log message:
Update to passenger 3.0.7
Ignore EINVAL from sigaltstack, seems to be what ruby itself does in 1.9
committing on behalf of jeremy@, who did all the work,
tested on i386 and tested packaging on amd64. All so I can commit a
simple nginx update... THANKS.
ok jasper

Log message:
Update to passenger 3.0.7
Ignore EINVAL from sigaltstack, seems to be what ruby itself does in 1.9
committing on behalf of jeremy@, who did all the work,
tested on i386 and tested packaging on amd64. All so I can commit a
simple nginx update... THANKS.
ok jasper

Log message:
Update to passenger 3.0.7
Ignore EINVAL from sigaltstack, seems to be what ruby itself does in 1.9
committing on behalf of jeremy@, who did all the work,
tested on i386 and tested packaging on amd64. All so I can commit a
simple nginx update... THANKS.
ok jasper

Log message:
Update to passenger 3.0.7
Ignore EINVAL from sigaltstack, seems to be what ruby itself does in 1.9
committing on behalf of jeremy@, who did all the work,
tested on i386 and tested packaging on amd64. All so I can commit a
simple nginx update... THANKS.
ok jasper

Log message:
Update to passenger 3.0.7
Ignore EINVAL from sigaltstack, seems to be what ruby itself does in 1.9
committing on behalf of jeremy@, who did all the work,
tested on i386 and tested packaging on amd64. All so I can commit a
simple nginx update... THANKS.
ok jasper

Log message:
Update to passenger 3.0.7
Ignore EINVAL from sigaltstack, seems to be what ruby itself does in 1.9
committing on behalf of jeremy@, who did all the work,
tested on i386 and tested packaging on amd64. All so I can commit a
simple nginx update... THANKS.
ok jasper

Log message:
REVISION bump all ruby ports due to a change in the pkgspec.
Previously, we were using ruby->=1.8,<=1.9, instead of
ruby->=1.8,<1.9. While this wouldn't cause an issue, since
our ruby-1.9.2 package isn't included in ruby->=1.8,<=1.9,
it's still wrong and should be fixed. This also fixes the
following minor issues:
Switch from using FLAVOR to MODRUBY_FLAVOR for *_DEPENDS.
Currently we don't have a ruby port that uses FLAVORs that
would differ from MODRUBY_FLAVOR, but it's possible we will
in the future.
Switch from BASE_PKGPATH to BUILD_PKGPATH in a few cases in
REGRESS_DEPENDS. This probably is not strictly necessary, but
BUILD_PKGPATH is used in more cases, so it is good for
consistency.
Switch to new style *_DEPENDS, with the version specification
at the end. The remaining cases where this is not done is
because a specific version is used.
Some FULLPKGNAME added to REGRESS_DEPENDS, to make sure that if
the old version is installed when you run a regress test, it
will install the new version first.
Some conversion of spaces to tabs for consistency.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Update ruby-passenger to 3.0.0. Switch the directory name from
phusion_passenger to phusion-passenger, since that's the name used
by upstream. Also tested by Pierre-Yves Ritschard.
OK landry@

Log message:
Handle the rest of the fallout from the splitting of MODRUBY_LIB_DEPENDS
into MODRUBY_WANTLIB and using CONFIGURE_STYLE = ruby gem ext. Use the
lang/ruby module for all dependent ports, setting
MODRUBY_{BUILD,RUN}DEP=No if necessary.
ok landry, phessler, sthen

Log message:
Bump all ruby ports not already handled.
In the upgrade from ruby 1.8.6 to 1.8.7, the PLISTs changed
due to differences in how RDoc processes files.
This also has a number of changes to the regress tests to
work with the changes to devel/ruby-rake. It moves most of
the regress tests to use MODRUBY_REGRESS.
OK jcs@, landry@, jasper@, sthen@

Log message:
The old version of boost included in this port assumes that GCC 4.1 and later
always provide the new atomic builtins. In reality those are only available
on hardware that provides the necessary atomic instructions. PA-RISC doesn't
have a suitable set of atomic instructions so work around it on hppa.
ok espie@, bernd@, landry@

Log message:
The old version of boost included in this port assumes that GCC 4.1 and later
always provide the new atomic builtins. In reality those are only available
on hardware that provides the necessary atomic instructions. PA-RISC doesn't
have a suitable set of atomic instructions so work around it on hppa.
ok espie@, bernd@, landry@