Provides for uninstalls and upgrades for installed ports.Ĭonfines ported software to a private “ sandbox” that keeps it from intermingling with
Or if you don't care about the Lua stuff at all, you can build wireshark without it.īTW, what exact operating system are your running, for which there is no RPM of an older Lua version available?Įdit: I should mention there's bug 10881 for this issue as well.Installs automatically any required support software, known as dependencies, for a given port. If you do care about compatibility, then you could download the source code for Lua 5.2 into some directory and build it, then point Wireshark to look in that directory if you're building with autotools, then during the configure stage you can set the path with the configure option ' -with-lua=/path/to/lua". To do that, grep for " lua_bitop" and remove the matching lines from the epan/wslua/Makefile.am or epan/wslua/CMakeLists.txt, depending on whether you use autotools or cmake and from epan/wslua/ remove the line matching " lua_bitop" as well as the line with " luaopen_bit" in it (and the lua_pop line after it). If you don't care about compatibility with others, then you could comment out the loading/compiling of the Bitop library ( lua_bitop.c).
(the Wireshark binaries shipped for MS-Windows and Mac-OSX are built with Lua 5.2) Even if the Lua Bitop library was modified to be able to compile/work with Lua 5.3, and whatever else in Wireshark that breaks with Lua 5.3 was fixed, we wouldn't be able to guarantee Lua scripts written by others would work in a Lua 5.3 engine nor that scripts written on a Lua 5.3-based Wireshark would work in other people's Wireshark programs running Lua 5.2. Wireshark can't be compiled with Lua 5.3.
0 kommentar(er)
