[MacPorts] #43917: ROOT6 : Update to first production release, 6.00.00

[MacPorts]

#43917: ROOT6 : Update to first production release, 6.00.00
-----------------------+---------------------------------
  Reporter:  jonesc@…  |      Owner:  mojca@…
      Type:  update    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:            |   Keywords:  haspatch maintainer
      Port:  root6     |
-----------------------+---------------------------------

Comment (by mojca@…):

 Replying to [comment:57 jeremyhu@…]:
 > Replying to [comment:42 mojca@…]:
 > > I'm using xcode 4.6.3. The return value seems to be
 > > {{{
 > > {clang llvm-gcc-4.2 apple-gcc-4.2 macports-clang-3.3}
 > > }}}
 > >
 > > No `macports-clang-3.4` there. And in fact 3.3 is always used if I
 disable the system clang (unless I blacklist `macports-clang-3.3`).
 >
 > What version do you have?
 >
 > r118085 r118735 r119034

 Version 2.3.0. The file says it's r118016, so it's indeed older. It must
 be this one:
 [browser:tags/release_2_3_0/base/src/port1.0/portconfigure.tcl]


 > The libcxx port provides the user with a way to install
 /usr/lib/libc++.dylib on Snow Leopard.  It's just a stub on Lion and
 later.
 > > I'll remove the part with pre-fetch and see what happens on 10.6.
 >
 > No, it's needed for Snow Leopard users if you're going to use libc++

 I'm confused now. Assuming that I use
 {{{
 depends_lib-append port:libcxx
 }}}
 Why do I still need to check for `[file exists /usr/lib/libc++.dylib]`
 then? To throw an error on 10.5 and 10.4? Or does it also make a
 difference on 10.6?

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