OSCommerce Product Manager for Windows
FS#171 - Licensing issue with OpenSSL libraries.
Attached to Project:
OSCommerce Product Manager
Opened by Mario A. Valdez-Ramirez (mvaldez) - Tuesday, 15 February 2005, 04:42 GMT
Last edited by Mario A. Valdez-Ramirez (mvaldez) - Tuesday, 15 February 2005, 13:01 GMT
Opened by Mario A. Valdez-Ramirez (mvaldez) - Tuesday, 15 February 2005, 04:42 GMT
Last edited by Mario A. Valdez-Ramirez (mvaldez) - Tuesday, 15 February 2005, 13:01 GMT
|
DetailsThe 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, 13:01 GMT
Reason for closing:
Tuesday, 15 February 2005, 13:01 GMT
Reason for closing:
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
SLP's installer is about 2.2 MB. Too big.
We can provide a very small installer customized for OSCPMWin.
And SLP's installer has a funny license. It's not an option.
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).
This has been already fixed.
Closed.