The last commit screwed up regress handling, by setting all ports with
MODRUBY_REGRESS to NO_REGRESS=Yes.  This should fix it.

Tested on amd64.  OKs?

Jeremy

Index: lang/ruby/ruby.port.mk
===================================================================
RCS file: /cvs/ports/lang/ruby/ruby.port.mk,v
retrieving revision 1.49
diff -u -p -r1.49 ruby.port.mk
--- lang/ruby/ruby.port.mk      2 Dec 2011 19:33:39 -0000       1.49
+++ lang/ruby/ruby.port.mk      5 Dec 2011 21:00:35 -0000
@@ -152,10 +152,12 @@ MODRUBY_BIN_RSPEC =       ${LOCALBASE}/bin/rsp
 .  endif
 .endif
 
-.if defined(MODRUBY_REGRESS) && !${MODRUBY_REGRESS:L:Mrspec} && \
-       !${MODRUBY_REGRESS:L:Mrspec2} && !${MODRUBY_REGRESS:L:Mrake} && \
-       !${MODRUBY_REGRESS:L:Mruby} && !${MODRUBY_REGRESS:L:Mtestrb}
+.if defined(MODRUBY_REGRESS)
+.  if !${MODRUBY_REGRESS:L:Mrspec} && \
+     !${MODRUBY_REGRESS:L:Mrspec2} && !${MODRUBY_REGRESS:L:Mrake} && \
+     !${MODRUBY_REGRESS:L:Mruby} && !${MODRUBY_REGRESS:L:Mtestrb}
 ERRORS += "Fatal: Unsupported MODRUBY_REGRESS value: ${MODRUBY_REGRESS}"
+.  endif
 .else
 .  if ${CONFIGURE_STYLE:L:Mextconf} || ${CONFIGURE_STYLE:L:Mgem} || \
        ${CONFIGURE_STYLE:L:Msetup}

Reply via email to