[Bug 470696] Review Request: rubygem-passenger - Passenger Ruby on Rails deployment system

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=470696

Bobby Powers <bobby at laptop.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bobby at laptop.org

--- Comment #88 from Bobby Powers <bobby at laptop.org> 2011-03-15 13:02:13 EDT ---
another reason to get it in Fedora, Hongli, is that your rpms are broken (bad
signature).  This was reported on your blog entry about the repos in January
and still happens for me as of last week.

Well, passenger 3 is out and none of the srpm or spec files listed above, so I
modified the latest srpm release to get something close to what we want I
think.  Since this original packaging request, it looks like the passenger
available through phusion's repos also bundles a version of nginx.  My changes
to the spec file basically are to remove that (as a consequence, it only builds
the apache plugin, not the nginx one as well).  The srpm is available at
http://dev.laptop.org/~bobbyp/passenger/rubygem-passenger-3.0.4-2.fc14.src.rpm
I'll attach the modified specfile (and a diff between the original and it) to
this bug.

It still has the vendored boost, but I'm hoping we can apply to get an
exemption as api and functionality has changed.  The biggest problem I see is
this note on [1]: 'If no attempt has been made to push the changes upstream, we
shouldn't be supporting people forking out of laziness'.

And if phusion won't allow us to use passenger, we can probably rename the
library to 'straphanger' or some such fairly easily.

Regards.


1 - http://fedoraproject.org/wiki/Packaging:No_Bundled_Libraries

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.