[MacPorts] #20775: gnustep-base: gnustep-config: command not found
MacPorts
noreply at macports.org
Thu Jun 26 14:17:29 PDT 2014
#20775: gnustep-base: gnustep-config: command not found
---------------------------+--------------------------------
Reporter: ryandesign@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 1.7.1
Resolution: | Keywords:
Port: gnustep-base |
---------------------------+--------------------------------
Comment (by egall@…):
Replying to [comment:29 ryandesign@…]:
> I cannot confirm or deny the statements made in that portfile. I would
be more inclined to believe that the portfile is completely out of date
and I think someone who understands gnustep or can spend the necessary
time to research it needs to come to a conclusion about what layout is
appropriate -- whether it be that which is currently embodied by the
gnustep_layout variant, that which is embodied by the fhs_layout variant,
or something else -- and make the port and its dependents unconditionally
use that.
I found a Portfile repo that one of the upstream GNUstep maintainers has
on GitHub, and they force the use of the gnustep layout, with this comment
explaining why the fhs layout will not work:
{{{
# we can not use the fhs layout, because that uses /opt/local/lib as the
GNUstep system library
# directory, and gnustep-make adds the system library directory to
DYLD_LIBRARY_PATH when
# GNUstep.sh is sourced.
# having /opt/local/lib in DYLD_LIBRARY_PATH can mess up macports. e.g.
pkg-config
# will stop working because it loads the macports libjpeg when it should
load the system
# libjpeg.
}}}
Source: [https://github.com/ericwa/gnustep-macports-
fixes/blob/master/gnustep/gnustep-make/Portfile#L27]
--
Ticket URL: <https://trac.macports.org/ticket/20775#comment:31>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list