From owner-freebsd-ports@FreeBSD.ORG  Thu Feb  6 20:05:20 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 6653AD3E
 for <ports@freebsd.org>; Thu,  6 Feb 2014 20:05:20 +0000 (UTC)
Received: from redundancy.redundancy.org (redundancy.redundancy.org
 [IPv6:2607:f2f8:a9c4::2])
 by mx1.freebsd.org (Postfix) with ESMTP id 48BE11FE1
 for <ports@freebsd.org>; Thu,  6 Feb 2014 20:05:20 +0000 (UTC)
Received: by redundancy.redundancy.org (Postfix, from userid 1001)
 id ACA2440E80C; Thu,  6 Feb 2014 12:05:19 -0800 (PST)
Date: Thu, 6 Feb 2014 12:05:19 -0800
From: David Thiel <lx@redundancy.redundancy.org>
To: Benjamin Podszun <benjamin.podszun@gmail.com>
Subject: Re: FreeBSD Port: prosody-0.8.2
Message-ID: <20140206200519.GN55007@redundancy.redundancy.org>
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+JOY=BPFgeCTJCaBgSqXSaQ3oNqE8HtCQ=FAMbg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAJOeo-3K-Fc+JOY=BPFgeCTJCaBgSqXSaQ3oNqE8HtCQ=FAMbg@mail.gmail.com>
X-OpenPGP-Key-fingerprint: 482A 8C46 C844 7E7C 8CBC 2313 96EE BEE5 1F4B CA13
X-OpenPGP-Key-available: http://redundancy.redundancy.org/lx.gpg
X-Face: %H~{$1~NOw1y#%mM6{|4:/<p]y9X%E+4%:1wo-M!re,
 zl.qH~yzbL-MWhtp$3QuKP&di/a{FOctD[FuX.\n4U*,
 M{TJg$oYp663.NyX!%H~~Tw$eR9xZU5W?1BM#t"a@'27^2x
User-Agent: Mutt/1.5.22 (2013-10-16)
Cc: ports <ports@freebsd.org>, Kurt Jaeger <pi@opsec.eu>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Feb 2014 20:05:20 -0000

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.