#38060 closed defect (fixed)
coreutils and gexpr should be marked as conflicting
| Reported by: | cooljeanius (Eric Gallager) | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
| Port: | coreutils gexpr |
Description
They both try to install an executable named gexpr into ${prefix}/bin. They're both nomaintainer.
Change History (3)
comment:1 Changed 12 years ago by larryv (Lawrence Velázquez)
| Version: | 2.1.3 |
|---|
comment:2 Changed 12 years ago by cooljeanius (Eric Gallager)
as far as I can tell... the url listed as gexpr's homepage is dead so I can't really research much further...
comment:3 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
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 programs 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
Note: See
TracTickets for help on using
tickets.
Replying to egall@…:
Is it the same program?