[MacPorts] #12794: MacPorts should warn of old Xcode versions

[MacPorts]

#12794: MacPorts should warn of old Xcode versions
--------------------------------------+-------------------------------------
  Reporter:  ryandesign at macports.org  |       Owner:  macports-dev at lists.macosforge.org
      Type:  defect                   |      Status:  new                              
  Priority:  Normal                   |   Milestone:  MacPorts base enhancements       
 Component:  base                     |     Version:  1.5.2                            
Resolution:                           |    Keywords:                                   
--------------------------------------+-------------------------------------
Comment (by jmpp at macports.org):

 > It now needs a matching runtime check when running port(1), to see that
 the required tools are installed and up to speed (e.g. check for "gcc"
 before running a build, for instance)


 A runtime check for an up-to-date OS and dev tools package would indeed be
 great. A comment and a couple of questions, though:

  -) I think it would be better to implement such check at the macports1.0
 level, probably as a part of the mportinit proc (so that any client
 initializing the API gets the safety check for free) or as a proc of its
 own in the macports1.0 namespace (preferable in my opinion, so that an API
 client is free to decide whether to check up-to-date'ness or not, as there
 are some clients that might not need it -- cf. PortIndex2MySQL).

  -) How do you plan for such checks to work? Do the just warn or bail out?
 (I'd prefer the former). How do we keep an always up-to-date knowledge of
 what dev tools release is current at whatever moment? How would these
 checks tie with what's already autoconf'd?

 -jmpp

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