Date: Wed, 12 Feb 2025 08:53:55 +0100 (CET) From: Ronald Klop <ronald-lists@klop.ws> To: list_freebsd@bluerosetech.com Cc: freebsd-ports@freebsd.org Subject: Re: How do I specify and attribute multiple licenses? Message-ID: <1988510304.13796.1739346835328@localhost> In-Reply-To: <57ce3279-00d5-3a92-38a8-42007ab2b0a8@bluerosetech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_13795_1648575965.1739346835265 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: list_freebsd@bluerosetech.com Datum: 11 februari 2025 20:44 Aan: freebsd-ports@freebsd.org Onderwerp: How do I specify and attribute multiple licenses? > > > I'm porting a PHP applicaton that, when fully installed, is actually 10 different components: the main application and 9 dependencies installed using Composer. To make the user's life easier, I want to distribute a tarball of the vendor files. Easy enough, but now I have to disclose all the licenses. I've already identified the licenses involved: > > - BSD 2-Clause "Simplified" License (BSD2CLAUSE) > - GNU General Public License v2.0 (GPLv2) > - GNU Lesser General Public License Version 3.0 (LGPL3) > - MIT License (MIT) > > All of them should let me do this kind of bundling and distributing, but I'm unsure how to disclose them to the end user. I've figured out I can do the license acceptance bit in the Makefile: > > LICENSE= GPLv2+ BSD2CLAUSE LGPL3+ MIT > LICENSE_COMB= multi > > But it's 10 different softwares, not 4. > > How do I attribute each component's license? > > Do get a copy of each license file and name those something specific under PREFIX/share/licenses? > > Is it sufficient to list which license is used by which in pkg-message? > > > > > The main purpose (IMHO) of the license in the ports tree is to specify if the distfile or package can be distributed. So as long as the licenses are similar in permissions I would keep it simple and use the pkg-message to list additional details. Keep it simple. You can always make things complicated in the future if there is a real necessity. Regards, Ronald. ------=_Part_13795_1648575965.1739346835265 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <html><head></head><body><br><p><small><strong>Van:</strong> list_freebsd@bluerosetech.com<br><strong>Datum:</strong> 11 februari 2025 20:44<br><strong>Aan:</strong> freebsd-ports@freebsd.org<br><strong>Onderwerp:</strong> How do I specify and attribute multiple licenses?<br></small></p><blockquote style="margin-left: 5px; border-left: 3px solid #ccc; margin-right: 0px; padding-left: 5px;"><div class="MessageRFC822Viewer do_not_remove" id="P"><!-- P --> <!-- processMimeMessage --><div class="TextPlainViewer do_not_remove" id="P.P"><!-- P.P -->I'm porting a PHP applicaton that, when fully installed, is actually 10 different components: the main application and 9 dependencies installed using Composer. To make the user's life easier, I want to distribute a tarball of the vendor files. Easy enough, but now I have to disclose all the licenses. I've already identified the licenses involved:<br> <br> - BSD 2-Clause "Simplified" License (BSD2CLAUSE)<br> - GNU General Public License v2.0 (GPLv2)<br> - GNU Lesser General Public License Version 3.0 (LGPL3)<br> - MIT License (MIT)<br> <br> All of them should let me do this kind of bundling and distributing, but I'm unsure how to disclose them to the end user. I've figured out I can do the license acceptance bit in the Makefile:<br> <br> LICENSE= GPLv2+ BSD2CLAUSE LGPL3+ MIT<br> LICENSE_COMB= multi<br> <br> But it's 10 different softwares, not 4.<br> <br> How do I attribute each component's license?<br> <br> Do get a copy of each license file and name those something specific under PREFIX/share/licenses?<br> <br> Is it sufficient to list which license is used by which in pkg-message?<br> <br> </div><!-- TextPlainViewer --> <hr> </div><!-- MessageRFC822Viewer --> </blockquote><br><br>The main purpose (IMHO) of the license in the ports tree is to specify if the distfile or package can be distributed.<div>So as long as the licenses are similar in permissions I would keep it simple and use the pkg-message to list additional details. </div><div>Keep it simple. You can always make things complicated in the future if there is a real necessity. </div><div><br></div><div>Regards,</div><div>Ronald.</div><div><br></div><div><br></div></body></html> ------=_Part_13795_1648575965.1739346835265--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1988510304.13796.1739346835328>