[MacPorts] #39517: globus-core: strange header install location

[MacPorts]

#39517: globus-core: strange header install location
-----------------------------+--------------------------------
 Reporter:  Peter.Danecek@…  |      Owner:  macports-tickets@…
     Type:  defect           |     Status:  new
 Priority:  Normal           |  Milestone:
Component:  ports            |    Version:  2.1.3
 Keywords:                   |       Port:  globus-core
-----------------------------+--------------------------------
 I am using Macports to install the globus toolkit. As most of the ports
 are not yet committed here, I use the version from
 https://github.com/dvandok/globus-macports. However, the issue I am
 reporting here relates to my understanding to the already committed port
 `globus-core`.

  This port installs the header file into `/opt/local/lib/globus/include`.
 Am I wrong, if I would think it should be simply `/opt/local/include`?

 Note: The other ports install header files into the correct location. So
 this seems an exception.

 {{{

 radegast:include petr$ pwd
 /opt/local/lib/globus/include
 radegast:include petr$ ls -la
 total 16
 drwxr-xr-x  3 root  admin   102 Jun 21 21:25 .
 drwxr-xr-x  3 root  admin   102 Jun 21 21:25 ..
 -rw-r--r--  1 root  admin  5609 Jun 14 14:28 globus_config.h
 radegast:include petr$ port provides globus_config.h
 /opt/local/lib/globus/include/globus_config.h is provided by: globus-core
 radegast:include petr$ port installed globus-core
 The following ports are currently installed:
   globus-core @8.9_0 (active)
 radegast:include petr$ port installed globus-core
 The following ports are currently installed:
   globus-core @8.9_0 (active)
 }}}

 I would assume this issue is related to this entry in the
 `configure.post_args`:

 {{{
 [...]
                         --with-
 flavorincludedir='\${libdir}/globus/include' \
 [...]
 }}}

 Any good reason for this?

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