[MacPorts] #50011: root6 - update to 6.06.00

[MacPorts]

#50011: root6 - update to 6.06.00
-----------------------+---------------------------------
  Reporter:  jonesc@…  |      Owner:  mojca@…
      Type:  update    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:            |   Keywords:  haspatch maintainer
      Port:  root6     |
-----------------------+---------------------------------

Comment (by mojca@…):

 Thanks a lot for the link. But it seems that ROOT 5 already fixed the
 problem in [https://github.com/root-
 mirror/root/commit/850a56cad37733694a6858314e30e3dafbacc220 850a56cad]
 (branch `v5-34-00-patches`).

 > I think I am personally still more in favour of enabling the C++14
 variant on all platforms, and force the use of MP's clang 3.7 where it is
 needed, simply because then this provides the same environment across all
 builds, but if Mojca you agree with jeremy then I can be arm twisted to
 only enable this on Xcode 6.3 and above.

 No need to break anybody's arm :)

 Whether or not it gets enabled by default, if the list of blacklisted
 compilers can get considerably shorter and allow macports-clang-3.4 as
 well as "native" compilers on some OS X versions, I would be in favour of
 introducing a variant.

 Personally I don't care about C++14 in the sense that I don't code in
 C++14 yet and during the buildbot outage I would prefer not to have to
 compile yet another clang/llvm version. I do acknowledge its importance
 for others though.

 From a very selfish point of view *I* would slightly prefer the option
 being switched off on the older systems for now, but on the other hand:
   * this would discourage other users who can fetch the binaries from the
 buildbot from rebuilding (and perhaps also using) ROOT6 with C++14 support
 by themselves
   * as soon as the ROOT team switches to clang-3.8 and if the clang dev
 team doesn't address the problems reported by Jeremy by then, we'll have
 to blacklist the old compilers anyway

 I leave the final decision about default variants to you (or potentially
 ask on the mailing list). I don't really care much either way. But I would
 be in favour of letting users to enable/disable C++14 and use an older
 compiler if they choose so. But we need to make sure that `+clang34`
 conflicts with `+c++14` or whatever the variant would be called (are
 pluses even legal?).

-- 
Ticket URL: <https://trac.macports.org/ticket/50011#comment:18>
MacPorts <https://www.macports.org/>
Ports system for OS X