Lucas <[email protected]> wrote: > Hello ports@, > > Find a update for net/prosody to 0.11.4. > > Lots of fixes and improvements happened since 0.11.2, which can be > found in [1] and [2]. In particular, there is a fix for closing a file > which can lead to "Too many open files", causing service disruption. > > Ports-wise, > > * Removed archivers/luazlib from MODLUA_RUN_DEPEDNS, as upstream > dropped official support for it since 0.9 and moved it to community > modules, with a security concerns comment. > * Removed -I...s from --ldflags > * Fixed patches/patch-util-src_table_c as it used arg unintialized. > Patch was added make it C99-compliant. > * Added patches/patch-util-src_pposix_c to shut up another C99 > warning. I don't know if I solve it the correct way(tm), in the > sense that I don't know the full implications of enabling > _BSD_SOURCE in there. Help is appreciated in that regard. > * Updated PLIST adding @so when needed. > * portcheck complaints with "the following libraries in WANTLIB look > like masked by RUN_DEPENDS: idn". make port-lib-depends-check and > make lib-depends-check says everything is fine, tho. Removing idn > from WANTLIB makes everyone happy, but I understand that every lib > the port needs should be in WANTLIB, so I left it there. I couldn't > find if any of the deps was pulling idn, so maybe it's just a false > positive? > * Take maintainership. > > Build and tested on amd64. > > [1]: https://prosody.im/doc/release/0.11.3 > [2]: https://prosody.im/doc/release/0.11.4 > > -Lucas
Forgot to ask: prosody doesn't support lua 5.3 officialy. Is there a way to limit lua to 5.2 here? I have seen devel/lua-bitop using FLAVORS = 5.2 FLAVOR ?= for limiting that, but I don't understand that mechanism.
