From owner-freebsd-ports@FreeBSD.ORG Wed Feb 3 15:56:14 2010 Return-Path: Delivered-To: freebsd-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34B23106566C for ; Wed, 3 Feb 2010 15:56:14 +0000 (UTC) (envelope-from alepulver@FreeBSD.org) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.freebsd.org (Postfix) with SMTP id C39968FC12 for ; Wed, 3 Feb 2010 15:56:13 +0000 (UTC) Received: (qmail 14310 invoked by uid 0); 3 Feb 2010 15:29:29 -0000 Received: from 190.231.116.248 (HELO ?10.0.0.3?) (190.231.116.248) by relay03.pair.com with SMTP; 3 Feb 2010 15:29:29 -0000 X-pair-Authenticated: 190.231.116.248 Message-ID: <4B699655.1080807@FreeBSD.org> Date: Wed, 03 Feb 2010 12:29:25 -0300 From: Alejandro Pulver User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: Dmitry Marakasov References: <4B6796F3.5030106@FreeBSD.org> <20100203011612.GD4178@hades.panopticon> In-Reply-To: <20100203011612.GD4178@hades.panopticon> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Doug Barton , "freebsd-ports@FreeBSD.org" Subject: Re: Plans for net-p2p/rblibtorrent*, and future of net-p2p/sharktorrent X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Feb 2010 15:56:14 -0000 On 2/2/2010 10:16 PM, Dmitry Marakasov wrote: > > I'll try to look into sharktorrent (if alepulver doesn't step > forward), and see if it can be updated to use libtorrent 0.14, I > think it'd be better to > I would appreciate if you can do that. > - switch it to rblibtorrent-devel > - remove rblibtorrent > - repocopy rblibtorrent-devel to rblibtorrent > - update rblibtorrent-devel to 0.15 and switch all ports to ("stable") > rblibtorrent > > not sure if there's enough history worth retaining, as this may be > shortened to just updating both ports to corresponding newer versions. > > If sharktorrent can't be fixed, we'll kave to keep rblibtorrent13 port > or remove both, however given that latest sharktorrent release was not > that long ago, I think the latter is not desirable. > IMHO it's better to have as fewer versions as possible, preferably one "stable" and one "devel". Of course in the case that most projects follow the development of rblibtorrent. Regards, Ale