From owner-freebsd-ports@FreeBSD.ORG Thu Jan 15 14:47:36 2015 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BEEA894B for ; Thu, 15 Jan 2015 14:47: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 89214BAA for ; Thu, 15 Jan 2015 14:47: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 t0FEkU5V082004; Thu, 15 Jan 2015 06:46:30 -0800 (PST) (envelope-from bsd-lists@bsdforge.com) To: Kurt Jaeger In-Reply-To: <20150115082729.GP44537@home.opsec.eu> References: <3a7891f4c67a054f13f9ba97f7fcd700@ultimatedns.net> <20150113192932.GL44537@home.opsec.eu> <21685.34336.390049.238359@gromit.timing.com> <11d948f20f5fedadc2570d82b6e7ec49@ultimatedns.net> , <20150115082729.GP44537@home.opsec.eu> From: "Chris H" Subject: Re: sysutils/bbcp: Anyone interesting in helping upgrade this port? Date: Thu, 15 Jan 2015 06:46:31 -0800 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <0c18c38876c88a9e21cd7e8fc568d545@ultimatedns.net> Content-Transfer-Encoding: 8bit Cc: FreeBSD Ports Mailing List , John Hein 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: Thu, 15 Jan 2015 14:47:36 -0000 On Thu, 15 Jan 2015 09:27:29 +0100 Kurt Jaeger wrote > Hi! > > > > So I won't be submitting the pr(1) until tomorrow. > > OK killed all the errors, rolled up a release, and submitted an > > svn diff. Please see the pr(1): > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196746 > > Testing @work. > > > The build still emits a fair amount of warnings. but none are > > show stoppers. > > Indeed, very noisy 8-} Linux-isms in/from errno.h && quoting issues in newer GCC's, but mostly CLANG. > > > I'll eliminate all the warnings, for the next version. > > Will you report those upstream ? As previously mentioned; upstream's code is fairly unmaintained (messy). In fact, I removed over 3,000 extraneous new-lines from one source file alone. Committing to maintain a port necessitated performing a mass code cleanup. If they (upstream) will accept a git push. Then we can still draw from upstream. Otherwise, I'll be forced to either 1) cherry-pick from upstream 2) fork/branch && rename the port/project After I squash the remaining warnings emitted, I submit a push request, and see where it goes. But it will involve every file in their source pool. So they may be reluctant. We'll see. :) Thanks for the prompt commit, and attention to this, Kurt! > > -- > pi@opsec.eu +49 171 3101372 5 years to go --Chris ---