[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





--- Comment #12 from Mamoru Tasaka <mtasaka at ioa.s.u-tokyo.ac.jp>  2008-11-11 03:38:59 EDT ---
(In reply to comment #8)
> (In reply to comment #7)
> > (In reply to comment #2)
> >
> > (...snip...)
> >
> > Unfortunately, there seems to be no easy way to fix Problem 2 (Problem 1 is
> > easy enough to fix by the rubygem-passenger upstream). All releases of the
> > mod_scgi code are under the CNRI license (although, changes made after 1.10 are
> > under MIT). Some methods of fixing this issue would be:
> > 
> > 1. Removing all of the copied code from mod_scgi 1.09, then replacing it either
> > with clean-room written code (aka, code written by someone who has never looked
> > at mod_scgi) or restructuring the rubygem-passenger code so that it is not
> > necessary. 
> > 
> Would another solution be to use mod_scgi >= 1.10?

Current mod_scgi seems 1.13.
http://python.ca/scgi/releases/scgi-1.13.tar.gz

However LICENSE.txt of mod_scgi 1.13 contains
--------------------------------------------------------------------
This version of the SCGI package is derived from scgi 1.10, released by
CNRI.  See doc/LICENSE_110.txt for the licensing terms of that release.
Changes made since that release are summarized in the CHANGES.txt file
along with a list of authors. Those changes are made available under the
following terms (commonly known as the MIT/X license).
--------------------------------------------------------------------
This reads that the codes derived from scgi 1.10 codes are still under
CNRI license, and only what is changed compared to 1.10 are under
MIT. So I don't think using latest mod_scgi will solve this issue.

-- 
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.