OSCommerce Product Manager

OSCommerce Product Manager for Windows
Tasklist

FS#171 - Licensing issue with OpenSSL libraries.

Attached to Project: OSCommerce Product Manager
Opened by Mario A. Valdez-Ramirez (mvaldez) - Monday, 14 February 2005, 22:42 GMT-6
Last edited by Mario A. Valdez-Ramirez (mvaldez) - Tuesday, 15 February 2005, 07:01 GMT-6
Task Type Bug Report
Category Backend / Core
Status Closed
Assigned To Mario A. Valdez-Ramirez (mvaldez)
Operating System All
Severity Very Low
Priority Immediate
Reported Version any
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The OpenSSL library has a license that looks incompatible with the GPL.

According to Debian-Legal, we cannot ship the OpenSSL DLLs along with OSCPMWin.

We can release a separate package and let the user do the mix, or we can include an exception in all licensing clauses about "we allow linking with OpenSSL, etc, etc".


These licensing issues are becoming very common in this project, huh?

As usual, this is a blocker bug.
This task depends upon

Closed by  Mario A. Valdez-Ramirez (mvaldez)
Tuesday, 15 February 2005, 07:01 GMT-6
Reason for closing:  
Comment by Mario A. Valdez-Ramirez (mvaldez) - Monday, 14 February 2005, 22:45 GMT-6
Solutions:


We can allow the installer to download the DLLs.

We can provide an installer to find the OSCPMWin location and drop the DLLs there.

We can provide the Win32 OpenSSL Installation Project: http://www.slproweb.com/products/Win32OpenSSL.html
Comment by Mario A. Valdez-Ramirez (mvaldez) - Monday, 14 February 2005, 22:48 GMT-6

SLP's installer is about 2.2 MB. Too big.

We can provide a very small installer customized for OSCPMWin.
Comment by Mario A. Valdez-Ramirez (mvaldez) - Monday, 14 February 2005, 22:52 GMT-6


And SLP's installer has a funny license. It's not an option.
Comment by Mario A. Valdez-Ramirez (mvaldez) - Monday, 14 February 2005, 22:59 GMT-6

Then we'll provide a zip package to be installed by hand (just like OSCPMWin) and an installer version to be installed in the OSCPMWin directory as automatically as possible (just like OSCPMWin installer).

Comment by Mario A. Valdez-Ramirez (mvaldez) - Tuesday, 15 February 2005, 07:01 GMT-6


This has been already fixed.
Closed.

Loading...