Omar Polo <o...@omarpolo.com> writes:
> this time with the tarball...
>
> Omar Polo <o...@omarpolo.com> writes:
>
>> Omar Polo <o...@omarpolo.com> writes:
>>
>>> Hello ports,
>>>
>>> I wanted to play with lua and ended up needing luarocks. I tried to
>>> resurrect the luarocks ports on openbsd-wip by abieber@ and cschutijser.
>>> With this I was able to install (locally) and use things like luasocket
>>> or dkjson, and even lua-lsp ^^
>>>
>>> I'm not sure about the FLAVORS bit, and I'm surely doing something wrong
>>> with the PKGNAME
>>>
>>> % cd /usr/ports/packages/amd64
>>> % find all -type f -name '*lua*'
>>> all/luarocks-3.7.0.tgz
>>> all/lua53rocks-3.7.0.tgz
>>> all/lua52rocks-3.7.0.tgz
>>>
>>> but otherwise seems functional. I opted to rename the `luarocks' and
>>> `luarocks-admin' executables so multiple flavors can be installed at the
>>> same time (seems useful).
>>>
>>> I'll try to upstream patch-src_luarocks_core_cfg_lua eventually.
>>>
>>> Thoughts/comments?
>>>
>>> Cheers,
>>>
>>> Omar Polo
>>>
>>
>> Here's an updated port with:
>>
>> - taking MAINTAINER (if nobody objects it)
>> - fixed PKGNAME, now it generates
>>
>> % find all -type f -name '*lua*'
>> all/luarocks-3.7.0-lua52.tgz
>> all/luarocks-3.7.0-lua53.tgz
>> all/luarocks-3.7.0-lua51.tgz
>> all/luarocks-3.7.0.tgz
>>
>> - followed what alpine does with the renaming: `luarocks' and
>> `luarocks-admin' are luarocks-${MODLUA_VERSION} and
>> luarocks-admin-${MODLUA_VERSION}
>>
>> The only doubt I still have is regarding the flavors: what's the point
>> of generating two equivalent packages? (luarocks and luarocks-lua51)
>>
Looks good to me! Might be worth adding a pkg/MESSAGE about creating a
symlink (similar to what we do for ruby).
OK abieber@ for import.
>> Cheers,
>
> [2. application/octet-stream; luarocks.tar.gz]...
