Date: Thu, 13 Jun 2013 12:21:47 +0200 From: Michael Gmelin <freebsd@grem.de> To: Eitan Adler <lists@eitanadler.com> Cc: freebsd-ports@freebsd.org Subject: Re: Are ports supposed to build and run on 10-CURRENT? Message-ID: <20130613122147.188ff95b@bsd64.grem.de> In-Reply-To: <CAF6rxgn1PR8mVGYtCrgh16Cpf9uBwdnqbhV=XXC0vME7uA%2BYEg@mail.gmail.com> References: <20130613031535.4087d7f9@bsd64.grem.de> <CAF6rxgn1PR8mVGYtCrgh16Cpf9uBwdnqbhV=XXC0vME7uA%2BYEg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 13 Jun 2013 08:07:14 +0200
Eitan Adler <lists@eitanadler.com> wrote:
> 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?
>
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130613122147.188ff95b>