Sorry but I didn't understand what you are trying to do properly but is
it an option to make a port for every dependency?
On 2/11/25 23:20, list_free...@bluerosetech.com wrote:
> On 2025-02-11 11:48, Yusuf Yaman wrote:
>> 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
> That won't work in this case, because it's not the port that fetches the
> dependencies, but Composer. The port fetches two distfiles:
>
> - the main application distfile
> - a tarball containing the other distributions
>
> I make the second distfile by running `composer install` myself then
> tarballing the vendor subdirectory. All four licenses apply to its
> contents.
