[MacPorts] #57895: coreutils: The BSD 'cut' command is still used despite specifying that the GNU version of 'cut' should be used by default instead
MacPorts
noreply at macports.org
Sat Jan 12 17:57:51 UTC 2019
#57895: coreutils: The BSD 'cut' command is still used despite specifying that the
GNU version of 'cut' should be used by default instead
---------------------------+-----------------------
Reporter: DanHam | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Keywords: coreutils cut | Port: coreutils
---------------------------+-----------------------
It looks as though the paths for GNU cut (installed as part of the
coreutils port) have been misconfigured. Unlike all other commands
installed by the port, the cut utility is installed under /opt/local/bin
with a prefix of 'gnu' rather than 'g'. Additionally, there is no 'non-
prefixed' link installed under /opt/local/libexec/gnubin.
Currently, the paths for GNU cut are configured as:
{{{
/opt/local/bin/gnucut
}}}
and
{{{
/opt/local/libexec/gnubin/gnucut
}}}
This means that the BSD version of cut (/usr/bin/cut) is used, even when
the user has added {{{/opt/local/libexec/gnubin}}} to the front of their
PATH variable. Somewhat confusingly, {{{$man cut}}} (correctly) displays
the page for the GNU version of cut.
I think the correct paths for GNU cut should instead be:
{{{
/opt/local/bin/gcut
}}}
With a symlink under /opt/local/libexec/gnubin pointing to the above of:
{{{
/opt/local/libexec/gnubin/cut
}}}
--
Ticket URL: <https://trac.macports.org/ticket/57895>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list