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

Am 2023-12-11 14:43, schrieb Guido Falsi:
> As a side note, if what you are trying to port is a pure PHP project 
> using composer, I'm not sure creating pa port of it is really a good 
> idea. The whole idea of composer is that it is handling dependencies 
> and also can be configured by the user with various tweaks. It is 
> preferable to "git clone" the project and manually run "composer 
> install" (or whatever is needed).

That's how I use what I want to port myself. But this is not very user 
friendly for those types which simply want to install a package and play 
with it.

> On the other hand, if what you're trying to port is a bigger project 
> with a php+composer part making a port could make sense, but why 
> upstream is not creating a proper distribution with all required files?

It's a plugin for the roundcube webmail package.

I don't like such external package things which can not be used by a 
distro-packaging mechanism... and saying that it is the responsability 
of upstream to provide something which can be used by a distro-packaging 
mechanism fails unfortunately at the reality (keeping this up-to-date in 
terms of security or changing APIs is a nightmare for a tiny 
hobby-project or something which is "good enough as it is, no real 
development going on"-stuff, so I understand if they tell that the 
install instructions include the run of composer)...

Bye,
Alexander.

-- 
http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org    netchild@FreeBSD.org  : PGP 0x8F31830F9F2772BF