On Tue, Feb 7, 2012 at 1:18 PM, Zachary Pincus <zachary.pincus@yale.edu> wrote: relevant readme when we cause the binaries to be downloaded. But another opinion might be useful, if you want to look at that license:
https://github.com/zachrahan/freeimage-sharedlib/blob/master/license-fi.txt
This license is very clear on the relevant points: "You may distribute the Executable version of Covered Code under a license of Your choice, which may contain terms different from this License, provided that You are in compliance with the terms of this License and that the license for the Executable version does not attempt to limit or alter the recipient's rights in the Source Code version from the rights set forth in this License. If You distribute the Executable version under a different license You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer or any Contributor. You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of any such terms You offer. 3.7. Larger Works. You may create a Larger Work by combining Covered Code with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You must make sure the requirements of this License are fulfilled for the Covered Code." I think we're perfectly safe, as long as we then provide the license file as well. In this case, we can even distribute skimage+freeimage package binaries without concern. Stéfan