[MacPorts] #63265: clang-11, clang-12, clang-devel: Don't default to +analyzer on 10.6 and earlier

[MacPorts]

#63265: clang-11, clang-12, clang-devel: Don't default to +analyzer on 10.6 and
earlier
-------------------------+-------------------------------------------
 Reporter:  ryandesign   |      Owner:  kencu
     Type:  enhancement  |     Status:  assigned
 Priority:  Normal       |  Milestone:
Component:  ports        |    Version:
 Keywords:               |       Port:  clang-11 clang-12 clang-devel
-------------------------+-------------------------------------------
 clang-3.7 no longer enables +analyzer by default on 10.6 and earlier as of
 [9809d4ba1a7540430d2f8998b211d39c69fc1587/macports-ports].

 clang-5.0, 6.0, 7.0, 8.0, 9.0, 10 and devel had the same change made in
 [6b338b8b0a4fd729e64d35829b0fa3b6d6711b5e/macports-ports].

 The change in clang-devel was reverted in
 [78b2cb450f7f56f0d1e6f66c44cd6e3a3fd742b1/macports-ports]. The commit
 message does not say why. Can it be re-reverted?

 clang-11 has used +analyzer as a default ever since the port was added.
 Can if be changed to do so only on OS > 10.6?

 clang-12 was added without that default variant but the default was added
 by request in [e5dd44494ea579bb4bc6b5b97ab3b8aa82087680/macports-ports].
 Can it be made conditional to OS > 10.6?

 (This all presumes that these clang ports can or will in the future build
 on <= 10.6.)

 If we could make these changes and agree that +analyzer shall not be a
 default for 10.6 and earlier, it would simplify the fixes that need to be
 made to the perl5 port to fix #57648.

-- 
Ticket URL: <https://trac.macports.org/ticket/63265>
MacPorts <https://www.macports.org/>
Ports system for macOS