From owner-freebsd-ports@FreeBSD.ORG  Fri Jun 14 12:36:12 2013
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 9799279B
 for <freebsd-ports@freebsd.org>; Fri, 14 Jun 2013 12:36:12 +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 E04DF1C97
 for <freebsd-ports@freebsd.org>; Fri, 14 Jun 2013 12:36:11 +0000 (UTC)
Received: (qmail 46771 invoked by uid 89); 14 Jun 2013 12:36:03 -0000
Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@194.97.158.66)
 by mail.grem.de with ESMTPA; 14 Jun 2013 12:36:03 -0000
Date: Fri, 14 Jun 2013 14:36:03 +0200
From: Michael Gmelin <freebsd@grem.de>
To: Matthias Apitz <guru@unixarea.de>
Subject: Re: Are ports supposed to build and run on 10-CURRENT?
Message-ID: <20130614143603.3c2a7837@bsd64.grem.de>
In-Reply-To: <20130613062417.GA868@tiny.Sisis.de>
References: <20130613031535.4087d7f9@bsd64.grem.de>
 <CAF6rxgn1PR8mVGYtCrgh16Cpf9uBwdnqbhV=XXC0vME7uA+YEg@mail.gmail.com>
 <20130613062417.GA868@tiny.Sisis.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=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Eitan Adler <lists@eitanadler.com>, freebsd-ports@freebsd.org
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.14
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: Fri, 14 Jun 2013 12:36:12 -0000

On Thu, 13 Jun 2013 08:24:18 +0200
Matthias Apitz <guru@unixarea.de> wrote:

> El d=C3=ADa Thursday, June 13, 2013 a las 08:07:14AM +0200, Eitan Adler
> escribi=C3=B3:
>=20
> > On Thu, Jun 13, 2013 at 3:15 AM, Michael Gmelin <freebsd@grem.de>
> > wrote:
> > > So my question is: Are we port maintainers now really supposed to
> > > make ports work with CURRENT?
> >=20
> > This is generally up to the maintainer; however many committers run
> > -CURRENT and test on that by default.
>=20
> This was a widely general question and a general answer too;
> I'm afraid that not all committers run tests with -CURRENT and on both
> architectures (amd64 and i386);
>=20
> at least for KDE4 I can confirm that it is unable to build on -CURRENT
> r250588 i386 due to:
>=20
> 1. certain required ports does not compile with clang
> 2. for kdelibs4 (and others) the tool automoc4 SIGSEGV randomly (i.e.
> for different source files and if you run it again it works)
>=20
> all this on a SVN clean ports tree;
>=20
> the current situation with CURRENT/clang/ports is highly a concern;
>=20
> 	matthias

To be perfectly honest, the fact that some committers seem to *solely*
test on CURRENT seems like bad QA practice to me.

--=20
Michael Gmelin