From: Klemens Nanni Subject: Re: NEW sysutils/openvox-server To: Sebastian Reitenbach , ports , Giovanni Bechis Date: Sat, 31 Jan 2026 13:58:09 +0000 28.01.2026 16:48, Sebastian Reitenbach пишет: > Hi,  > > cat pkg/DESCR:  > OpenVox is configured in an agent-server architecture, in which a > primary server node manages the configuration information for a fleet of > agent nodes. OpenVox Server acts as the primary server node. OpenVox > Server is a Ruby and Clojure application that runs on the Java Virtual > Machine (JVM). OpenVox Server runs Ruby code for compiling Puppet > catalogs and for serving files in several JRuby interpreters. It also > provides a certificate authority through Clojure. > > It is a drop in replacement for Puppetserver. > > with that, the legacy sysutils/puppetserver/8 port could bite the dust. The version there is loooong time EOL. That'd be nice. > > between OpenVox server 8.11.x and 8.12.x they removed the Makefile, therefore the old Makefile is taken and stored in the files section. otherwise, could implement it directly in the do-install: section in the ports Makefile. But I found this way easier and a bit cleaner, but if there are concerns, I'd take it on and migrate the target into the do-install: if necessary. See my openvoxdb response. In addition to that - MODJAVA_RUN_DEPENDS is not needed in RUN_DEPENDS, the java module already does that - as mentioned in openvoxserver-ca, I suggest dropping ruby flavors, so the dep here would need adjusting - SUBST_CMD purely on WRKSRC files seems odd, why not do that in post-patch? This files/Makefile looks simpler and lots of repeated lines could definitely be merged with globbing or .for loops in make, which would result in a perhaps shortish, but still simple and boring do-install. Then we don't need gmake and stuff like 'rundir = /var/run' and 'rm -rf ${PREFIX}/var' would cancel themselves out. > > Similarly to the puppetserver structure, to eventually support multiple versions, using the same openvoxserver/ structure. > > other than that, comments, test reports, or any other feedback welcome. > > thanks, > Sebastian