Are ports supposed to build and run on 10-CURRENT?
freebsd at grem.de
Fri Jun 14 12:36:12 UTC 2013
On Thu, 13 Jun 2013 08:24:18 +0200
Matthias Apitz <guru at unixarea.de> wrote:
> El día Thursday, June 13, 2013 a las 08:07:14AM +0200, Eitan Adler
> > On Thu, Jun 13, 2013 at 3:15 AM, Michael Gmelin <freebsd at grem.de>
> > 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.
> 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);
> at least for KDE4 I can confirm that it is unable to build on -CURRENT
> r250588 i386 due to:
> 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)
> all this on a SVN clean ports tree;
> the current situation with CURRENT/clang/ports is highly a concern;
To be perfectly honest, the fact that some committers seem to *solely*
test on CURRENT seems like bad QA practice to me.
More information about the freebsd-ports