From owner-freebsd-ports@FreeBSD.ORG Tue Jan 13 19:11:36 2015 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0489E205 for ; Tue, 13 Jan 2015 19:11:36 +0000 (UTC) Received: from udns.ultimatedns.net (ultimatedns.net [209.180.214.225]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 917A0CB7 for ; Tue, 13 Jan 2015 19:11:35 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t0DJAIiB070184; Tue, 13 Jan 2015 11:10:19 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: Freddie Cash In-Reply-To: References: , From: "Chris H" Subject: Re: sysutils/bbcp: Anyone interesting in helping upgrade this port? Date: Tue, 13 Jan 2015 11:10:22 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <3a7891f4c67a054f13f9ba97f7fcd700@ultimatedns.net> Content-Transfer-Encoding: 8bit Cc: FreeBSD Ports Mailing List , jhein@symmetricom.com X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jan 2015 19:11:36 -0000 On Tue, 13 Jan 2015 10:43:15 -0800 Freddie Cash wrote > On Tue, Jan 13, 2015 at 10:17 AM, Chris H wrote: > > > On Tue, 13 Jan 2015 10:08:05 -0800 Freddie Cash wrote > > > > > Good morning, > > > > > > With the requirement for the NONE cipher in OpenSSH requiring a custom > > > compile of the world or a custom compile of the openssh-portable port > > (all > > > my production servers are binary-package-only now), I've started using > > bbcp > > > instead of "zfs send" over SSH. And looking at using bbcp instead of > > rsync > > > over SSH for another system (transfer speed is more important than > > > encrypting the data as the transfer is done over a very local LAN link). > > > > > > The bbcp port is version 20120520; the latest version available is > > > 20140902. There have been several new features added over the past 2 > > years > > > that make it (at least on paper) a decent rsync replacement for our uses. > > > > > > Is there anyone interested in bringing this port up-to-date. I had a > > quick > > > look, but it requires some C hacking that's beyond my skills. :( I've > > > only tried compiling it with clang, which gives lots of errors. Haven't > > > tried with gcc, though. > > > > > > I just had a look. Looks interesting. I can't foresee any issue > > moving it ahead. But before I step up, and say "I'll take it". > > Have you contacted the maintainer? I don't want to step on any toes. :) > > > > ​Well, now I feel sheepish. > > I was looking at the freshports.org page for it and just saw > portmgr-related commits to the port and assumed it was maintained by > "freebsd-ports" (aka not maintained). I completely missed the little > "Maintainer" line at the top. :( > > I've CC'd the port Maintainer to bring them into the loop.​ > > > ​[Being a past port maintainer, I really should know better.]​ LOL No worries. :) I checked out (cloned) the master branch, and looked it over. This will be an easy upgrade, and I'll be happy to do it. Should the maintainer not mind, that is. ;) All the best! > > > -- > Freddie Cash > fjwcash@gmail.com > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" --Chris ---