#32516: Remove macfuse port --------------------------------------+------------------------------------- Reporter: anatol.pomozov@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: macfuse --------------------------------------+------------------------------------- Hi, I propose to remove macfuse port (or replace it with a dumb stub that installs fuse4x as a dependency). The reasons are following: - macfuse officially declared itself as a dead project. See its official page http://code.google.com/p/macfuse/ it recommends to use its forks instead. - fuse4x fork exists and actively used/developed for more that 6 months already. This is default fuse implementation both in macports and homebrew. - people still have problems on macports+macfuse. Here is a recent example of it https://groups.google.com/d/topic/osxfuse- group/WOT0x3gBN5Q/discussion some people complain that they cannot use CurlFtpFs+macports+macfuse and it was suggested to uninstall macports' version of macfuse and use macfusion application instead. The right answer here is to install fuse4x port instead of macfuse. fuse4x port fixes the issue described in the message. If that person had fuse4x then there should not be any issues. -- Ticket URL: <https://trac.macports.org/ticket/32516> MacPorts <http://www.macports.org/> Ports system for Mac OS