#38060: coreutils and gexpr should be marked as conflicting ------------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: coreutils gexpr | ------------------------------+-------------------------------- Changes (by larryv@…): * version: 2.1.3 => Comment: Replying to [ticket:38060 egall@…]:

They both try to install an executable named `gexpr` into `${prefix}/bin`.

Is it the same program? -- Ticket URL: <https://trac.macports.org/ticket/38060#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS

#38060: coreutils and gexpr should be marked as conflicting ------------------------------+-------------------------------- Reporter: egall@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: coreutils gexpr | ------------------------------+-------------------------------- Changes (by ryandesign@…): * status: new => closed * cc: ryandesign@… (added) * resolution: => fixed Comment: The coreutils port install GNU expr, and in MacPorts, we prefix all the coreutils program names with "g" so that they do not shadow the BSD versions of those same problems that OS X provides, which would lead to badness. GNU expr works e.g. like this: {{{ $ gexpr 1 + 2 3 }}} The gexpr port installs an independently-developed program called gexpr which functions differently: {{{ $ gexpr "1 + 2" 3 }}} So yes, they are different, and should conflict with one another. r103138 -- Ticket URL: <https://trac.macports.org/ticket/38060#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS