cc'ing ports for the benefit of other readers, list archives, etc. On 2024/11/07 17:31, Lydia Sobot wrote: > Hi, > > I am trying to package Bookstack for OpenBSD and can't seem to find how to > deal > with a program that uses Composer to handle its dependencies; is it automatic > with the lang/php module? Do they have to explicitly be added as ports > themselves? Something else? > > Thanks in advance for your advice, > ~Lydia Sobot.
Generally for PHP web apps installable easily by following upstream docs we don't package them. For example we don't have drupal, mediawiki, wordpress, piwik, tt-rss, etc (either never had, or in some cases removed). There are still some in packages, mostly where patches are needed or they're a bit more fiddly (e.g. librenms), and a few which weren't removed (nextcloud which is now giving us headaches as their eol and upgrade policy don't align well with OpenBSD releases). Unless there's significant value to having ports, or patches are needed to get them to work, I think we'd mostly prefer not to add more. If bookstack does fit in the "fiddly/needs patches" category then, to answer the question about deps using composer, we handle this by preparing supplementary distfiles. net/librenms and mail/roundcubemail have examples.
