[MacPorts] #29917: Fuse4X: add port
MacPorts
noreply at macports.org
Mon Jul 18 09:39:44 PDT 2011
#29917: Fuse4X: add port
--------------------------------------+-------------------------------------
Reporter: anatol.pomozov@… | Owner: dports@…
Type: submission | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version:
Keywords: | Port: fuse4x fuse4x-kext fuse4x-framework
--------------------------------------+-------------------------------------
Comment(by anatol.pomozov@…):
> macfuse and fuse4x won't actually be able to coexist -- at least not in
MacPorts because both of them want to install `$prefix/include/fuse.h` in
the same place.
I see following solutions in this solution:
1) Add fuse4x port first. It is going to conflict with macfuse (because of
headers and fuse.pc file). But it is ok, as nobody should install fuse4x
(this is just a library that other programs depend on). Once fuse4x is
added - change all other program dependencies to fuse4x as one step. It is
needed to avoid conflict when both macfuse and fuse4x installed. Right
after that remove macfuse port.
2) Change fuse.pc to fuse4x.pc and ./include/*.h location to
./include/fuse4x/*.h It requires patches from macports but in this case
there will be no conflicts at all. Then one-by-one migration can be
started. After it is done - macfuse port should be removed, fuse.pc added
as a link to fuse4x.pc, all dependent ports should change dependency from
fuse4x.pc to fuse.pc. Then fuse4x.pc and ./include/fuse4x/*.h be removed
(including patches from macports). This way requires more time and
efforts though.
--
Ticket URL: <https://trac.macports.org/ticket/29917#comment:41>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list