Hi,
Can you see Porter's Handbook 5.8.7 LICENSE_DISTFILES and
LICENSE_DISTFILES_NAME.
If you have multiple distribution files, then this maybe work for you.
Example 38. LICENSE_DISTFILES
Used when the distribution files do not all have the same license. For
example, one has a code
license, and another has some artwork that cannot be redistributed:
MASTER_SITES= SF/some-game
DISTFILES= ${DISTNAME}${EXTRACT_SUFX} artwork.zip
LICENSE= BSD3CLAUSE ARTWORK
LICENSE_COMB= dual
LICENSE_NAME_ARTWORK= The game artwork license
LICENSE_TEXT_ARTWORK= The README says that the files cannot be
redistributed
LICENSE_PERMS_ARTWORK= pkg-mirror pkg-sell auto-accept
LICENSE_DISTFILES_BSD3CLAUSE= ${DISTNAME}${EXTRACT_SUFX}
LICENSE_DISTFILES_ARTWORK= artwork.zip
On 2/11/25 22:43, list_free...@bluerosetech.com wrote:
> 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?
>
