FS#46189 - [lua] Add 'staticlibs' option to package
Attached to Project:
Arch Linux
Opened by Pierre Chapuis (catwell) - Thursday, 03 September 2015, 14:26 GMT
Last edited by Caleb Maclennan (alerque) - Wednesday, 20 September 2023, 07:13 GMT
Opened by Pierre Chapuis (catwell) - Thursday, 03 September 2015, 14:26 GMT
Last edited by Caleb Maclennan (alerque) - Wednesday, 20 September 2023, 07:13 GMT
|
Details
Description:
The Lua package explicitly builds and installs liblua.a, and then strips it out because it does not have the "staticlibs" option. I think it would be a good idea to add that option to the PKGBUILD, or otherwise make it clearer that liblua.a is not going to be installed. |
This task depends upon
Closed by Caleb Maclennan (alerque)
Wednesday, 20 September 2023, 07:13 GMT
Reason for closing: Fixed
Additional comments about closing: 5.4.6-2
Wednesday, 20 September 2023, 07:13 GMT
Reason for closing: Fixed
Additional comments about closing: 5.4.6-2
Please provide more information behind this argument. Why it is a good idea? What problems it suppose to fix?
It doesn't really bother me if you don't ship the static library though, it is easy to rebuild myself. However I was puzzled because the PKGBUILD installs the static library at the packaging step (make TO_LIB="liblua.a ..." install). I suggest removing liblua.a from TO_LIB since it will be stripped out later.
Reassign to the current maintainer? If this line should be adjusted or not?
In regards of adding staticlibs there weren't breaking packages reported so alone in that regard this issue could be closed.
__________
[0] https://github.com/archlinux/svntogit-packages/blob/4d745dc13992534be6bb02df4d1ab052fbdc4a0e/trunk/PKGBUILD#L41