<div dir="ltr">By the way, this would be a perfect question for the new Github Discussions feature! If you would not mind moving some version of this question there, I will copy my answer, as it would be nice to have it easily available for the next time it comes up. Having it sitting there on Github with the source code would be convenient and at some point, this mailing list will be shut down in favor of Discussions anyway. Thanks!<div><br></div><div>Cheers,</div><div><br></div><div>Ted</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Nov 17, 2020 at 2:38 AM Jan-Willem Goossens <<a href="mailto:jhmgoossens@hotmail.com">jhmgoossens@hotmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto">
<div dir="ltr">Ted,</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Thank you for the elaborate answer. </div>
<div dir="ltr">For my builds from source code repos (without coin brew) this is very clear indeed:no third party code. </div>
<div dir="ltr">Whenever I will build from a stable release’s tarball, I’ll verify what’s in the tarball.</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">Thanks again for your help. </div>
<div dir="ltr">Jan-Willem</div>
<div dir="ltr"><br>
</div>
<div dir="ltr"><br>
</div>
<div dir="ltr">
<blockquote type="cite">On 17 Nov 2020, at 06:37, Ted Ralphs <<a href="mailto:ted@lehigh.edu" target="_blank">ted@lehigh.edu</a>> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div>Hi all,</div>
<div><br>
</div>
We are pretty careful with licensing in general. No source from any of the third-party dependencies are included in any repo within the "coin-or" Github organization. All projects in the Optimization Suite are entirely licensed under the EPL. We use the term
"Third Party" specifically to mean software that may be under a different license and/or copyright and that we therefore do not redistribute ourselves. We do link to available third-party libraries when they are already present on the user's machine. For the
most part, it is up to the user to be aware of this.
<div><br>
</div>
<div>There are separate projects within the "coin-or-tools" Github organization that provide convenience scripts for downloading and building the source for some of these third-party dependencies. If you use the convenience scripts, it is up to you to be aware
of the licenses of the downloaded code. If you use the coinbrew script to fetch a project and its dependencies, some of these convenience scripts may be run automatically. Currently, coinbrew does download third-party sources by default. I'm slowly rolling
out a more nuanced dependency specification system that will categorize third-party packages as "optional" or "recommended" and will not download optional packages by default. If coinbrew downloads and builds any third-party codes automatically, you may end
up with some of these dependencies as part of your self-built binary. </div>
<div><br>
</div>
<div>You can prevent download of any third party source code by coinbrew by adding the argument "--no-third-party", but this will not prevent the configure script from finding certain libraries that are already installed on your system and linking to them.
That should not be an issue unless you build and redistribute a static executable, which could then possibly include parts of the dependent libraries. To prevent this, you would need to use the appropriate arguments to the configure scripts to suppress use
of particular libraries. If you are building with shared libraries, then it is easy to verify with "ldd" what libraries are being linked to, including both those that are present on the system, e.g., were installed using a package manager, and those that
were built using our wrappers. </div>
<div><br>
</div>
<div>As for the distributed binaries, the answer may vary, depending on the specific version and platform. We've been evolving our recipe over time according to feedback. For non-static binaries, it's easy to check what exactly is distributed by checking the
contents of the archive after downloading (though again, there is a chance the code might use a shared library already installed on your system under Linux, for example). For static binaries, you would need to check the recipe used to generate the binary,
which would be in either the travis.yml or appveyor.yml configuration files for Linux/OS X and Windows, respectively. </div>
<div><br>
</div>
<div>Sorry for the somewhat convoluted answer, but hopefully, this gives you all the information you need. Hope this helps and feel free to follow up with any further questions. <br>
</div>
<div><br>
</div>
<div>Cheers,</div>
<div><br>
</div>
<div>Ted</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, Nov 16, 2020 at 2:11 PM Jan-Willem Goossens <<a href="mailto:jhmgoossens@hotmail.com" target="_blank">jhmgoossens@hotmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US">
<div>
<p class="MsoNormal"><span lang="EN-GB">Dear all,<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">Sorry for the partial email earlier.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">In short: Is it correct that none of non-EPL-licensed optional components (GLPK, etc.) are included in the source repo of CBC and related dependencies?<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">I build CBC and its dependencies (Cbc, Clp, Cgl, Osi, CoinUtils, BuildTools) from the master branch of their repos.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">These all mention EPL v2 as license in their root folder’s LICENSE file.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-GB">However, optional components exist such as
</span>GLPK, GNU Readline, GNU History, AMPL Solver Library (ASL), BLAS and LAPAC (etc.) that use different licenses, and that I therefore want to avoid.
<u></u><u></u></p>
<p class="MsoNormal">Maybe a silly question, but such components are _<i>not</i>_ in the normal repos (like
<a href="https://github.com/coin-or/cbc" target="_blank">https://github.com/coin-or/cbc</a>), or are they?
<u></u><u></u></p>
<p class="MsoNormal">And as a consequence, these optional components are not in my self-built CBC.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thank you for your help.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Jan-Willem<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
_______________________________________________<br>
Cbc mailing list<br>
<a href="mailto:Cbc@list.coin-or.org" target="_blank">Cbc@list.coin-or.org</a><br>
<a href="https://list.coin-or.org/mailman/listinfo/cbc" rel="noreferrer" target="_blank">https://list.coin-or.org/mailman/listinfo/cbc</a><br>
</blockquote>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">Dr. Ted Ralphs<br>
Professor, Industrial and Systems Engineering<br>
Lehigh University<br>
(610) 628-1280<br>
ted 'at' lehigh 'dot' edu<br>
<a href="http://coral.ie.lehigh.edu/~ted" target="_blank">coral.ie.lehigh.edu/~ted</a><br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Dr. Ted Ralphs<br>Professor, Industrial and Systems Engineering<br>Lehigh University<br>(610) 628-1280<br>ted 'at' lehigh 'dot' edu<br><a href="http://coral.ie.lehigh.edu/~ted" target="_blank">coral.ie.lehigh.edu/~ted</a><br></div></div></div></div></div></div></div></div>