Date: Fri, 14 Jun 2013 14:36:03 +0200 From: Michael Gmelin <freebsd@grem.de> To: Matthias Apitz <guru@unixarea.de> Cc: Eitan Adler <lists@eitanadler.com>, freebsd-ports@freebsd.org 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%2BYEg@mail.gmail.com> <20130613062417.GA868@tiny.Sisis.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130614143603.3c2a7837>