1 | | There are some things that could be done to make it clearer that the `gmake` port is GNU Make. First, while the `description` field in `gmake`'s portfile makes it clear that it is GNU Make, the `long_description` field does not do likewise. Second, the port could install a symlink to the `gmake` binary named "`gnumake`" so that one could just type `gnumake` to get the MacPorts `gnumake` instead of the Apple one. Also, while you're at it ("it" being making symlinks to the `gmake` binary), you could also make another symlink to `gmake` in `${prefix}/libexec/gnubin`, which is where a lot of other GNU tools put un-"g"-prefixed symlinks to their binaries. |
| 1 | There are some things that could be done to make it clearer that the `gmake` port is GNU Make. First, while the `description` field in `gmake`'s portfile makes it clear that it is GNU Make, the `long_description` field does not do likewise. Second, the port could install a symlink to the `gmake` binary named "`gnumake`" so that one could just type `gnumake` to get the MacPorts `gnumake` instead of the Apple one. Also, while you're at it ("it" being making symlinks to the `gmake` binary), you could also make another symlink to `gmake` in `${prefix}/libexec/gnubin`, which is where a lot of other GNU tools put un-"`g`"-prefixed symlinks to their binaries (I have it added to my `$PATH`) |