[MacPorts] #48613: About root6 dependencies

[MacPorts]

#48613: About root6 dependencies
-------------------------------+--------------------------------
 Reporter:  graziosi.angelo@…  |      Owner:  macports-tickets@…
     Type:  defect             |     Status:  new
 Priority:  Normal             |  Milestone:
Component:  ports              |    Version:  2.3.3
 Keywords:  root6, gcc         |       Port:  root6
-------------------------------+--------------------------------
 In my previous MacPorts installation (Yosemite 10.0.4), I installed root6
 with:


 {{{
 sudo port install root6 +avahi +fftw3 +fitsio +gcc5 +ldap +mysql56 +odbc
 +postgresql92 +pythia +python34 +sqlite3 +vc +xrootd
 }}}

 and only gcc5 compiler was installed


 {{{
 port installed | grep gcc
 gcc5 @5.2.0_0 (active)
   gcc47 @4.7.4_5 (active)
   gcc_select @0.1_8 (active)
   gsl @1.16_3+gcc5 (active)
   libgcc @5.2.0_0 (active)
   pdftk @2.02_0+gcc47 (active)
   py27-numpy @1.9.2_2+gcc5 (active)
   root6
 @6.04.02.99_0+avahi+cocoa+fftw3+fitsio+gcc5+graphviz+gsl+http+ldap+minuit2+mysql56+odbc+opengl+postgresql92+pythia+python34+roofit+soversion+sqlite3+ssl+tmva+vc+xml+xrootd
 (active)
 }}}

 Now, I did a new Yosemite 10.10.5 installation (from scratch) and
 reinstalled MacPorts. This time, I saw that root6 has gcc5 variant by
 default so I installed root6 with:


 {{{
 sudo port install root6 +avahi +cxx14 +fftw3 +fitsio +ldap +mysql56 +odbc
 +postgresql92 +pythia +python34 +sqlite3 +vc +xrootd
 }}}

 adding the cxx14 variant and removing the explicit call "+gcc5". Now it
 has installed also gcc49:


 {{{
 [...]
 --->  Computing dependencies for root6
 --->  Dependencies to be installed: avahi dbus-python27 dbus-glib gtk3 at-
 spi2-atk at-spi2-core xorg-libXi xorg-inputproto xorg-libXfixes xorg-
 fixesproto xorg-libXtst xorg-recordproto atk hicolor-icon-theme libepoxy
 mesa xorg-dri2proto xorg-glproto xorg-libXdamage xorg-damageproto xorg-
 libXmu xorg-libXcomposite xorg-compositeproto xorg-libXcursor xorg-
 libXinerama xorg-xineramaproto xorg-libXrandr xorg-randrproto libdaemon
 libglade2 gtk2 py27-gdbm py27-pygtk py27-cairo py27-gobject py27-numpy
 gcc49 cctools llvm-3.5 libcxx llvm_select cloog isl gcc_select ld64
 ld64-latest libgcc libmpc mpfr py27-cython cython_select py27-nose
 nosetests_select cfitsio cmake curl libarchive lzo2 py34-sphinx
 py34-alabaster python34 python3_select py34-babel py34-setuptools py34-tz
 py34-docutils py34-roman py34-jinja2 py34-markupsafe py34-pygments
 py34-six py34-snowballstemmer py34-sphinx_rtd_theme sphinx_select gcc5
 giflib graphviz gd2 xpm gts libnetpbm libLASi xorg-libXaw gsl libiodbc
 libpqxx postgresql92 ossp-uuid postgresql_select readline lzma mysql56
 mysql_select tcp_wrappers openldap cyrus-sasl2 kerberos5 libcomerr db46
 icu pythia boost root_select xrootd libevent swig
 [...]
 }}}


 {{{
 port installed | grep gcc
   gcc49 @4.9.3_0 (active)
   gcc_select @0.1_8 (active)
   [...]
 }}}


 It seems that adding cxx14 variant has triggered this.. Is really so?
 What's happening?

 I wonder if there is a better way to handle this.

 For example, I notice that in my previous installation I had:


 {{{
 port installed | grep num
   py27-numpy @1.9.2_2+gcc5 (active)
 }}}

 Instead now,


 {{{
 port installed | grep num
   py27-numpy @1.9.2_2+gfortran (active)
 }}}


 Which gfortran?


 Thanks,
  Angelo.

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