ports/184673: abort when a dependency's ports directory doesn't exist

[Viktor Štujber]

>Number:         184673
>Category:       ports
>Synopsis:       abort when a dependency's ports directory doesn't exist
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Wed Dec 11 01:30:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator:     Viktor Štujber
>Release:        9.1
>Organization:
>Environment:
FreeBSD 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0 r251958M: Wed Jun 19 01:33:28 CEST 2013
>Description:
While installing a port, the system will check for dependencies and will try to install any that are missing using the ports tree. If the port's directory does not exist, Mk/bsd.port.mk will just print "No directory for $$prog.  Skipping.." and continue with the main build.

The build will most likely fail somewhere down the line. If you're not actively watching/logging the build output, that will be the only indication that something went wrong. A hypothetical configure script might even work around the missing dependency and silently build an incomplete or inferior product.

I suggest changing all places that do this 'skipping' thing to instead abort the build. Or at least have a way to configure this behavior (although I can't think of a reason why one would want to continue).
>How-To-Repeat:

>Fix:


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