[MacPorts] #56093: compiler-blacklist-versions: simplify clang blacklisting by associating Apple clang versions with macports-clang versions

[MacPorts]

#56093: compiler-blacklist-versions: simplify clang blacklisting by associating
Apple clang versions with macports-clang versions
--------------------------+-----------------
  Reporter:  kencu        |      Owner:
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:
      Port:  clang        |
--------------------------+-----------------

Comment (by kencu):

 Replying to [comment:2 ryandesign]:
 > So if your program requires "clang 3.6 or newer", how do you know
 whether 602.0.53 was far enough along in the development cycle of clang
 3.6 to have the required feature or not?

 A fine example. So the proposal would be that:
 {{{
 compiler.blacklist {clang < 602}
 }}}
 would also implicitly add
 {{{
 complier.blacklist-append macports-clang-3.3 macports-clang-3.4 macports-
 clang-3.5
 }}}
 as those are (basically) sure not to work aa well.

 I wonder if this would get close enough to the desired behaviour for the
 vast majority of cases to prove helpful. So often you see the Portfile
 authour first adding the clang blacklisting, and then later on going back
 to add all the individual macports-clang versions once it is realized they
 are not able to build the software as well.

 It could be overridden in the Portfile for some specific bootstrap case if
 needed.

--
Ticket URL: <https://trac.macports.org/ticket/56093#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS