[MacPorts] #14220: Warn or handle deactivated dependencies

[MacPorts]

#14220: Warn or handle deactivated dependencies
----------------------------------------+-----------------------------------
 Reporter:  saul.hazledine at bbsrc.ac.uk  |       Owner:  macports-tickets at lists.macosforge.org
     Type:  enhancement                 |      Status:  new                                  
 Priority:  Low                         |   Milestone:  MacPorts base enhancements           
Component:  ports                       |     Version:  1.6.0                                
 Keywords:  activate dependencies       |  
----------------------------------------+-----------------------------------
 In the situation where a new port, A, is being installed and depends on a
 port B.

 If B is installed (but deactivated) A will start installing and then hit
 an error during the build. The error appears as a build error to the
 untrained eye.

 As a new user, I thought there was an error with the port and raised a
 ticket when none needed to be raised. I feel bad about this but suspect I
 wasn't the first person to install on a deactivated dependency and then
 get a build error.

 There are many different behaviours that could be less confusing to people
 like myself. As a suggestion though, would it be possible to warn the user
 if a dependency was deactivated?

-- 
Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14220>
MacPorts </projects/macports>
Ports system for Mac OS