Hi,
After having read several posts regarding the inclusion of LGPL'ed libraries with software that is licensed under another license than GPL or LGPL, there is still one point that confuses me.
The way I understand it, there should normally be no problem to include the .php-files (and the README and the LICENSE files) in my distribution and require_once() the LGPL'ed library from my MIT/X11-licensed PHP-script.
However, since the library depends on other software to perform it's function, the path variables in the script must be manually modified.
In order to make the installation of my script as easy as possible for the end user, I would like to make an installation-script that prompts the user for these paths (as well as performing necessary steps to configure the installation of the script I've written, including choosing a MySQL-database and creating the necessary tables).
The way I see it, there are two ways of doing this without violating the LGPL:
1) Have the installation script modify the library-files directly, releasing the installer under LGPL whilst releasing the rest of my code under MIT/X11, or
2) Modify the library so that it has an installer of it's own (releasing this modification under LGPL), that can I can include_once() in my main (MIT/X11-licensed) installer.
I would prefer to go with the second option.
Any thoughts?