Re: Example for port which needs to run php-composer?

On 12/12/23 11:21, Alexander Leidinger wrote:
> Am 2023-12-11 21:19, schrieb Guido Falsi:
> 
>> I gave you suggestions on how to work around these 
>> (properties|features|limitations|rules|whatever) of the ports tree. I 
>> would be more interested to hear if you found those useful or not.
> 
> Distributing the dependencies as an additional tarball via the FreeBSD 
> commiters local distfiles feature is a possible workaround to the 
> problem. If I want to go that way... I haven't decided yet. It would 

I agree it is not idea, but given the nature of tools like composer and 
npm I don't think there is any other option.

> shift the responsability for those to me (as a maintainer), or to us (as 
> a project), compared to having the dependencies as separate ports (as a 
> maintainer I would at least get the benefit of 
> portscout/repology/freshports mails) or bundled by the author of the 
> software I want to port.

Depending on the upstream project practices, they could be distributing 
a lock file, so you would be distributing whatever they "locked" at 
release time, which is the intended use for dependency manager lock files.

-- 
Guido Falsi <mad@madpilot.net>