> > or the "and" word glues these two licenses together ? > > Yes, you can choose the license to be MIT. Typically, you would use > both, but since releasing it under GPL-3+ would make it non-free, you > should use only the MIT license.
And what about a situation where: - package A MIT links to SSL - package B GPL links to package A - package B does not link to SSL in confgure.ac or during complation Yet, ldd package B shows libssl ? It is a violation ? -- Dariusz Dwornikowski, Institute of Computing Science, Poznań University of Technology www.cs.put.poznan.pl/ddwornikowski/ room 2.7.2 BTiCW | tel. +48 61 665 29 41 -- To UNSUBSCRIBE, email to debian-legal-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140811090425.ga30...@blackstar.cs.put.poznan.pl
