On Thu, 13 Jun 2013 08:07:14 +0200
Eitan Adler <li...@eitanadler.com> wrote:

> On Thu, Jun 13, 2013 at 3:15 AM, Michael Gmelin <free...@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
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Reply via email to