Arch Linux User Repository

use_unbound.lua does not exist :(

Is included in the install file:

RunScript 'use\_unbound.lua'

This package should depend on Prosody explicitly because it's installing the library to its tree

I did not do anything, I just asked what the difference was :$

You guys didn't even fucking look at the PKGBUILD before the merge don't lol me.

I already laid out all the differences. Do whatever you want.

@jprjr sorry for having caused the merge lol

@fordprefect can you address the issues reported by jprjr?

Hi all, I responded to the merge request email, I'm just posting it here as well, but point 4 is updated with more info on package naming conventions.

Before proceeding with deleting the lua-unbound package please address the following issues in luaunbound:

1. luaunbound only builds for the latest Lua version (at this time, 5.4). lua-unbound builds for Lua 5.1, 5.2, 5.3, and current.

2. luaunbound has unnecessary make dependencies mercurial, libxslt, ccache, and an unnecessary install script.

3. Said install script references another package (prosody) and has nothing to do with the lua module.

4. In the original email I stated "luaunbound does not follow lua module naming convention." After reviewing the wiki, I don't see a defined convention for Lua modules, but it seems most lua modules use "lua-(modulename)", "lua51-(modulename)", etc.

Technically I don't think lua-unbound follows the convention, since the actual module name is luaunbound. There seems to be some discrepancies even in lua modules in the community repos, some examples:

luaossl is listed on luarocks as luaossl, and in the community repo as lua-luaossl, but installs as a module named openssl.

luasocket is listed on luarocks as luasocket, but in the community repo it's lua-socket, and installs a module named socket.

Since this is listed on luarocks as luaunbound and the actual, installed module is also named luaunbound, it probably makes sense to use the somewhat-redundant lua-luaunbound, lua51-luaunbound, etc names.

1. (this should be point 5, markdown is re-rendering this as 1) luaunbound's optdepends lists luajit - but the luaunbound C module does not do anything differently when running under luajit. Plus since it's not built for Lua 5.1, luajit is unable to use the module.

Forgot to mention luaunbound's optdepends lists luajit - but the lua-unbound C module does not do anything different when running under luajit. Plus since it's not built for Lua 5.1, luajit is unable to use the module.

@abouvier - this is a split package that supports building for multiple Lua versions, the current luaunbound only builds for the latest Lua version.

luaunbound has unnecessary make dependencies mercurial, libxslt, ccache, and an unnecessary install script.

Additionally this follows the lua module naming scheme, luaunbound does not.

@abouvier, jhass: I have filed a merge request. makes sense to keep only one.

@abouvier Probably none. Compare the first submitted dates, this one 2016-04-23, lua-unbound got 2022-03-31