On 23/01/07 04:33, Lucas wrote: > Ashlen <euryd...@riseup.net> wrote: > > On 23/01/06 12:53, Omar Polo wrote: > > > This needs some further testing. Packages that depends on luasockets > > > are > > > > > > - devel/luacopas no test suite > > > - devel/luaevent test run OK > > > - net/jitsi/prosody-plugins no test suite > > > - net/prosody no test suite > > > - security/luasec no test suite > > > - www/luakit with simple runtesting seems fine > > > > > > I can manage to test it with net/prosody on -RELEASE but will take a > > > while. > > > > I'll see if I can test against net/prosody on -RELEASE as well, actually. > > I'll > > do my best to follow your suggestions. Thank you for taking the time to > > respond. > > Prosody port maintainer here. Built and installed it with op@ patch in > my -current and restarted prosody. It didn't blow up and is currently > connected to my usual servers. Running with LD_DEBUG shows it's actually > used (is there a better way to check which dynamic libraries a running > process is using? fstat doesn't provide that info :( ) > > dlopen: loading: /usr/local/lib/lua/5.3/socket/unix.so > flags /usr/local/lib/lua/5.3/socket/unix.so = 0x0 > head /usr/local/lib/lua/5.3/socket/unix.so > obj /usr/local/lib/lua/5.3/socket/unix.so has > /usr/local/lib/lua/5.3/socket/unix.so as head > linking /usr/local/lib/lua/5.3/socket/unix.so as dlopen()ed > head [/usr/local/lib/lua/5.3/socket/unix.so] > examining: '/usr/local/lib/lua/5.3/socket/unix.so' > tail /usr/local/lib/lua/5.3/socket/unix.so > protect RELRO [0x6810b52eba0,0x6810b530000) in > /usr/local/lib/lua/5.3/socket/unix.so > doing ctors obj 0x680e98f65f0 @0x6810b52d0b0: > [/usr/local/lib/lua/5.3/socket/unix.so] > dlopen: /usr/local/lib/lua/5.3/socket/unix.so: done (success). > dlsym: luaopen_socket_unix in /usr/local/lib/lua/5.3/socket/unix.so: > 0x6810b52cf60 > > -Lucas >
Thanks Lucas, I was actually a little wary of trying to build an updated version of net/luasocket against 7.2. I'm still really new to this stuff. net/prosody depends on security/luasec, so if I understand it correctly, that means devel/luacopas and net/jitsi/prosody-plugins are the ones left untested. As for the renaming thing, I realized I didn't actually provide any links showing why I kept this in. I looked at the commits and it appears their rationale is that anyone that writes a Lua script and imports luasocket as well as another module that happens to have an identical buffer_* will have a headache due to name collisions. Though if that's the case, it makes me wonder why FreeBSD backed out the patch in the commit op@ mentioned. https://cvsweb.openbsd.org/ports/net/luasocket/patches/patch-src_buffer_c?rev=1.2&content-type=text/x-cvsweb-markup https://marc.info/?l=freebsd-ports-bugs&m=125089202109336&w=2 https://marc.info/?l=freebsd-ports&m=125097467421558&w=2 As for the dynamic library thing, I'm unsure. I know about ldd(1) but that's not for a running program. Maybe some of the tracing software available, like ltrace(1) or similar, could do it.
