<div dir="ltr">I've never given that a thought. I have a few projects on my GitHub account that have multiple licences. I've never had any issues with it. A user, as I remember, needs to pick one and use that with their code, so theoretically they should never clash because the user is only using one of the ones the publisher offers.<div><br></div><div>~Carl</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Oct 13, 2021 at 9:49 AM Peter Soper via TriEmbed <<a href="mailto:triembed@triembed.org">triembed@triembed.org</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> <span style="font-family:monospace">Crud. Change the first "if yes" to "if no". Sorry for the confusion.</span>
<br>
<div>
<br>
<p>Oct 13, 2021 9:47:03 AM Triangle Embedded Interest Group <<a href="mailto:TriEmbed@triembed.org" target="_blank">TriEmbed@triembed.org</a>>:</p>
<blockquote> <span style="font-family:monospace">Is it the case that mixing permissive-licensed code (eg BSD,MIT) with GPL3 licensed code can get you into legal trouble in some regions of the world? What if the GPL code sticks to LGPL3 where you can point to the library boundaries between that code and more permissive-licensed code also in it's own library (but in an embedded context where static linking is the only option)? If yes, is that nuked if your "main" module is GPL3 licensed? By nuked I mean rendering the whole program as having to be subject to GPL3 rules. If the above is hazardous then if all the GPL3 code involved is kept in a public repo (or sets of repis that segregate by license type) is that likely to satisfy EVERYBODY and render the code non-hazardous to the maintainers of the repo(s)? I'm trying to figure out long term legal hazards for code that will be used in arbitrary countries (eg the EU) as well as in the US, Iran: wherever. This issue gates what off the shelf open source can be used vs what has to be written if no OSS code with license permissivity flavor X can be found. We could perhaps follow up on this as a November "problem of the month" at the November 8 meeting.</span>
<br> <span style="font-family:monospace">Pete (IANAL)</span>
<br>
<div>
_______________________________________________
<br>Triangle, NC Embedded Computing mailing list
<br>
<br>To post message: <a href="mailto:TriEmbed@triembed.org" target="_blank">TriEmbed@triembed.org</a>
<br>List info: <a href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org" target="_blank">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a>
<br>TriEmbed web site: <a href="http://TriEmbed.org" target="_blank">http://TriEmbed.org</a>
<br>To unsubscribe, click link and send a blank message: mailto:<a href="mailto:unsubscribe-TriEmbed@bitser.net" target="_blank">unsubscribe-TriEmbed@bitser.net</a>?subject=unsubscribe
<br>
</div>
</blockquote>
</div>
</div>
_______________________________________________<br>
Triangle, NC Embedded Computing mailing list<br>
<br>
To post message: <a href="mailto:TriEmbed@triembed.org" target="_blank">TriEmbed@triembed.org</a><br>
List info: <a href="http://mail.triembed.org/mailman/listinfo/triembed_triembed.org" rel="noreferrer" target="_blank">http://mail.triembed.org/mailman/listinfo/triembed_triembed.org</a><br>
TriEmbed web site: <a href="http://TriEmbed.org" rel="noreferrer" target="_blank">http://TriEmbed.org</a><br>
To unsubscribe, click link and send a blank message: mailto:<a href="mailto:unsubscribe-TriEmbed@bitser.net" target="_blank">unsubscribe-TriEmbed@bitser.net</a>?subject=unsubscribe<br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">--------------------------------------------------------------<br>Carl J. Nobile (Software Engineer/API Design)<br><a href="mailto:carl.nobile@gmail.com" target="_blank">carl.nobile@gmail.com</a><br>--------------------------------------------------------------</div></div>