Binary name conflict with FreeBSD's ipfs tool

FreeBSD has a command called ipfs which is part of the firewall tooling: http://www.unix.com/man-page/FreeBSD/8/ipfs/
That's also why the port is called ipfs-go.

ipfs-update needs to take this into account.

cc @Aranjedeath

[erkinalp]

Then call the FreeBSD port interplanetaryfilesystem.

[gammazero]

The problem is not the name of the FreeBSD port ipfs-go, but the name of the binary installed by that port (/usr/local/bin/ipfs-go) versus the name of the binary installed/upgraded by ipfs-update (/usr/local/bin/ipfs).

The reason the FreeBSD port installs the binary as ipfs-go is to avoid the conflict with the /sbin/ipfs utility on FreeBSD. This issue is asking that the naming used by the port (ipfs-go) is also recognized by ipfs-update when installing/upgrading on FreeBSD.

If ipfs-update needs to be port-aware on FreeBSD...
When installing on FreeBSD, if ipfs-go is installed, then ipfs-update should tell the user to update using the ports or pkg system, or first uninstall the ipfs-go package before using ipfs-update. ipfs-update should not try to update an instance of ipfs-go installed via ports, since that would leave the older port installed, but with a newer binary that was not from the port.