From owner-freebsd-ports@FreeBSD.ORG Thu Jun 13 10:22:57 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4E004206 for ; Thu, 13 Jun 2013 10:22:57 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 991CB13B0 for ; Thu, 13 Jun 2013 10:22:56 +0000 (UTC) Received: (qmail 19131 invoked by uid 89); 13 Jun 2013 10:22:55 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@93.215.186.42) by mail.grem.de with ESMTPA; 13 Jun 2013 10:22:55 -0000 Date: Thu, 13 Jun 2013 12:21:47 +0200 From: Michael Gmelin To: Eitan Adler Subject: Re: Are ports supposed to build and run on 10-CURRENT? Message-ID: <20130613122147.188ff95b@bsd64.grem.de> In-Reply-To: References: <20130613031535.4087d7f9@bsd64.grem.de> X-Mailer: Claws Mail 3.9.1 (GTK+ 2.24.18; amd64-portbld-freebsd9.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jun 2013 10:22:57 -0000 On Thu, 13 Jun 2013 08:07:14 +0200 Eitan Adler wrote: > On Thu, Jun 13, 2013 at 3:15 AM, Michael Gmelin > wrote: > > So my question is: Are we port maintainers now really supposed to > > make ports work with CURRENT? > > This is generally up to the maintainer; however many committers run > -CURRENT and test on that by default. > > I would add something like > .if ${OSVERSION} > ${WHEREEVERITBROKE} > BROKEN= Unit tests fail > .endif > to the port's Makefile. > Thanks for your helpful response. I followed your advice and filed a new version of the patch marking it BROKEN for 10: http://www.freebsd.org/cgi/query-pr.cgi?pr=179233#reply4 I will look into making the port work on 10 as soon as we have an actual release date and the C++ compiler tool chain stabilized, so that I'm not dealing with a moving target, -- Michael Gmelin