Date: Thu, 6 Feb 2014 12:05:19 -0800 From: David Thiel <lx@redundancy.redundancy.org> To: Benjamin Podszun <benjamin.podszun@gmail.com> Cc: ports <ports@freebsd.org>, Kurt Jaeger <pi@opsec.eu> Subject: Re: FreeBSD Port: prosody-0.8.2 Message-ID: <20140206200519.GN55007@redundancy.redundancy.org> In-Reply-To: <CAJOeo-3K-Fc%2BJOY=BPFgeCTJCaBgSqXSaQ3oNqE8HtCQ=FAMbg@mail.gmail.com> References: <1391697997.2043.5.camel@TIS-Ben-T520.local> <20140206150619.GV2951@home.opsec.eu> <CAJOeo-3UCy9aa3qHPvgc3yKsO0YuTCPG-cY6BfwJV0NSrRYRdQ@mail.gmail.com> <20140206185532.GK55007@redundancy.redundancy.org> <CAJOeo-3K-Fc%2BJOY=BPFgeCTJCaBgSqXSaQ3oNqE8HtCQ=FAMbg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/06, Benjamin Podszun wrote: > Maybe I can help with that - since I plan to migrate/relocate and > that's a core part of what I need here (which is why I'm diving into > ports about 30min after my first FreeBSD installation in years). So - > one tester, ready to help out. ;-) Thanks! > Luasocket: Well, can you explain what you mean? Are you talking about > luasec including luasocket (and again, in a prerelease 3.x version)? If you > could tell me a bit more I'd be happy to invest some time/give it a go. Ugh, I forgot about this part of the mess. So, Prosody says that Luasocket 2 is "required", but the new Luasec includes luasocket 3. Do we update the Luasocket port to 3, hosted on its new GitHub repo? Does this mean that the updated Luasec and luasocket ports would actually conflict with each other? If you know or can find those answers, that'd be useful.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140206200519.GN55007>