ports/68569: bsd.ruby.mk should not use `.error'

[Oliver Eikemeier]

>Number:         68569
>Category:       ports
>Synopsis:       bsd.ruby.mk should not use `.error'
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jul 01 20:30:31 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator:     Oliver Eikemeier
>Release:        FreeBSD 4.10-STABLE i386
>Organization:
Fillmore Labs - http://www.fillmore-labs.com
>Environment:
System: FreeBSD nuuk.fillmore-labs.com 4.10-STABLE

>Description:

bsd.ruby.mk uses `.error' in multiple places:

  117:.error You set the variable RUBY to "${RUBY}", but it does not seem to exist.  Please specify an already installed ruby executable.
  122:.error You set the variable RUBY to "${RUBY}", but it failed to include rbconfig.  Please specify a properly installed ruby executable.
  146:.error "Ruby 1.7 is obsolete; set RUBY_VER to 1.8 instead."

This has the ill effect that a misconfigured port breaks all port tools,
like INDEX building, pkg_version, portupgrade, chkversion and others.

I assume that tools that should report these misconfigurations, like
portsmon, are affected too.

Most port tools use make -V to extract information fro the ports,
so FreshPorts can do make -VPKGNAME -VBROKEN and could display that
port PKGNAME is broken because BROKEN.

Common practice in the ports tree is to set BROKEN in this case.

>How-To-Repeat:
>Fix:

Replace `.error' with `BROKEN='

>Release-Note:
>Audit-Trail:
>Unformatted: