<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>[119125] trunk/dports/fuse</title>
</head>
<body>

<style type="text/css"><!--
#msg dl.meta { border: 1px #006 solid; background: #369; padding: 6px; color: #fff; }
#msg dl.meta dt { float: left; width: 6em; font-weight: bold; }
#msg dt:after { content:':';}
#msg dl, #msg dt, #msg ul, #msg li, #header, #footer, #logmsg { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt;  }
#msg dl a { font-weight: bold}
#msg dl a:link    { color:#fc3; }
#msg dl a:active  { color:#ff0; }
#msg dl a:visited { color:#cc6; }
h3 { font-family: verdana,arial,helvetica,sans-serif; font-size: 10pt; font-weight: bold; }
#msg pre { overflow: auto; background: #ffc; border: 1px #fa0 solid; padding: 6px; }
#logmsg { background: #ffc; border: 1px #fa0 solid; padding: 1em 1em 0 1em; }
#logmsg p, #logmsg pre, #logmsg blockquote { margin: 0 0 1em 0; }
#logmsg p, #logmsg li, #logmsg dt, #logmsg dd { line-height: 14pt; }
#logmsg h1, #logmsg h2, #logmsg h3, #logmsg h4, #logmsg h5, #logmsg h6 { margin: .5em 0; }
#logmsg h1:first-child, #logmsg h2:first-child, #logmsg h3:first-child, #logmsg h4:first-child, #logmsg h5:first-child, #logmsg h6:first-child { margin-top: 0; }
#logmsg ul, #logmsg ol { padding: 0; list-style-position: inside; margin: 0 0 0 1em; }
#logmsg ul { text-indent: -1em; padding-left: 1em; }#logmsg ol { text-indent: -1.5em; padding-left: 1.5em; }
#logmsg > ul, #logmsg > ol { margin: 0 0 1em 0; }
#logmsg pre { background: #eee; padding: 1em; }
#logmsg blockquote { border: 1px solid #fa0; border-left-width: 10px; padding: 1em 1em 0 1em; background: white;}
#logmsg dl { margin: 0; }
#logmsg dt { font-weight: bold; }
#logmsg dd { margin: 0; padding: 0 0 0.5em 0; }
#logmsg dd:before { content:'\00bb';}
#logmsg table { border-spacing: 0px; border-collapse: collapse; border-top: 4px solid #fa0; border-bottom: 1px solid #fa0; background: #fff; }
#logmsg table th { text-align: left; font-weight: normal; padding: 0.2em 0.5em; border-top: 1px dotted #fa0; }
#logmsg table td { text-align: right; border-top: 1px dotted #fa0; padding: 0.2em 0.5em; }
#logmsg table thead th { text-align: center; border-bottom: 1px solid #fa0; }
#logmsg table th.Corner { text-align: left; }
#logmsg hr { border: none 0; border-top: 2px dashed #fa0; height: 1px; }
#header, #footer { color: #fff; background: #636; border: 1px #300 solid; padding: 6px; }
#patch { width: 100%; }
#patch h4 {font-family: verdana,arial,helvetica,sans-serif;font-size:10pt;padding:8px;background:#369;color:#fff;margin:0;}
#patch .propset h4, #patch .binary h4 {margin:0;}
#patch pre {padding:0;line-height:1.2em;margin:0;}
#patch .diff {width:100%;background:#eee;padding: 0 0 10px 0;overflow:auto;}
#patch .propset .diff, #patch .binary .diff  {padding:10px 0;}
#patch span {display:block;padding:0 10px;}
#patch .modfile, #patch .addfile, #patch .delfile, #patch .propset, #patch .binary, #patch .copfile {border:1px solid #ccc;margin:10px 0;}
#patch ins {background:#dfd;text-decoration:none;display:block;padding:0 10px;}
#patch del {background:#fdd;text-decoration:none;display:block;padding:0 10px;}
#patch .lines, .info {color:#888;background:#fff;}
--></style>
<div id="msg">
<dl class="meta">
<dt>Revision</dt> <dd><a href="https://trac.macports.org/changeset/119125">119125</a></dd>
<dt>Author</dt> <dd>dports@macports.org</dd>
<dt>Date</dt> <dd>2014-04-17 15:29:01 -0700 (Thu, 17 Apr 2014)</dd>
</dl>

<h3>Log Message</h3>
<pre>fuse4x-*: replaced_by osxfuse (#39456)</pre>

<h3>Modified Paths</h3>
<ul>
<li><a href="#trunkdportsfusefuse4xPortfile">trunk/dports/fuse/fuse4x/Portfile</a></li>
<li><a href="#trunkdportsfusefuse4xframeworkPortfile">trunk/dports/fuse/fuse4x-framework/Portfile</a></li>
<li><a href="#trunkdportsfusefuse4xkextPortfile">trunk/dports/fuse/fuse4x-kext/Portfile</a></li>
<li><a href="#trunkdportsfuseosxfusePortfile">trunk/dports/fuse/osxfuse/Portfile</a></li>
</ul>

<h3>Removed Paths</h3>
<ul>
<li>trunk/dports/fuse/fuse4x/files/</li>
<li>trunk/dports/fuse/fuse4x-kext/files/</li>
</ul>

</div>
<div id="patch">
<h3>Diff</h3>
<a id="trunkdportsfusefuse4xPortfile"></a>
<div class="modfile"><h4>Modified: trunk/dports/fuse/fuse4x/Portfile (119124 => 119125)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/dports/fuse/fuse4x/Portfile        2014-04-17 22:22:49 UTC (rev 119124)
+++ trunk/dports/fuse/fuse4x/Portfile        2014-04-17 22:29:01 UTC (rev 119125)
</span><span class="lines">@@ -3,73 +3,12 @@
</span><span class="cx"> 
</span><span class="cx"> PortSystem          1.0
</span><span class="cx"> 
</span><ins>+replaced_by         osxfuse
+PortGroup           obsolete 1.0
+
</ins><span class="cx"> name                fuse4x
</span><span class="cx"> version             0.9.2
</span><del>-revision            1
-set tag             [string map {. _ } $version]
</del><ins>+revision            2
</ins><span class="cx"> categories          fuse devel
</span><span class="cx"> platforms           macosx
</span><span class="cx"> maintainers         dports
</span><del>-description         A FUSE-Compliant File System Implementation Mechanism \
-                    for Mac OS X
-
-long_description    Fuse4X implements a mechanism that makes it          \
-                    possible to implement a fully functional file        \
-                    system in a user-space program on Mac OS X. It       \
-                    aims to be API-compliant with the FUSE               \
-                    (File-system in USErspace) mechanism that            \
-                    originated on Linux.  Therefore, many existing       \
-                    FUSE file systems become readily usable on Mac OS    \
-                    X. This port provides the user-space library and     \
-                    header files for building filesystems.
-
-homepage            http://fuse4x.github.io/
-license             LGPL
-master_sites        https://github.com/fuse4x/fuse/tarball/fuse4x_${tag}
-
-checksums           sha256  82b7591d7079c1076737b3efbf16d61cc6e31bffaca45d29fa888d7847191f08 \
-                    rmd160  d0356ecedc06b0ea6599e45023f0a95c8ee851e3
-
-extract.mkdir       yes
-extract.post_args   &quot;| tar --strip-components=1 -xf -&quot;
-
-patchfiles          patch-include_fuse_param.h.diff
-
-# kext destination: kext will be installed into ${kextdir}/fuse4x.kext.
-#
-# The kext is autoloaded by the library using load_fuse4x, so it
-# doesn't have to go into /System/Library/Extensions. It doesn't
-# matter where we put it, as long as it's kept in sync with the library.
-#
-# If updating the patchfile or ${kextdir}, must also update the
-# corresponding patch in the fuse4x-kext port!
-set kextdir        &quot;${prefix}/Library/Extensions&quot;
-post-patch {
-    reinplace &quot;s|@@KEXTPATH@@|${kextdir}/fuse4x.kext|&quot; ${worksrcpath}/include/fuse_param.h
-
-    # Fuse4X normally installs its library as libfuse4x.dylib to allow
-    # it to co-exist with MacFUSE, but the ports are conflicting so we
-    # don't need to worry about that. Instead, we'll install it as
-    # libfuse.dylib so dependent ports don't need to be modified.
-    reinplace &quot;s|-lfuse4x|-lfuse|&quot; ${worksrcpath}/fuse.pc.in
-    reinplace &quot;s|libfuse4x|libfuse|g&quot; ${worksrcpath}/lib/Makefile.am
-    reinplace &quot;s|libfuse4x.la|libfuse.la|&quot; ${worksrcpath}/example/Makefile.am
-
-    # automake 1.13 compatibility (see #37451)
-    file mkdir ${worksrcpath}/m4
-    reinplace &quot;s|AM_CONFIG_HEADER|AC_CONFIG_HEADERS|&quot; ${worksrcpath}/configure.in
-}
-
-configure.cflags-append -D_DARWIN_USE_64_BIT_INODE
-configure.ldflags   -framework CoreFoundation
-
-use_autoreconf      yes
-autoreconf.args     -fvi
-
-depends_build       port:pkgconfig port:autoconf port:automake port:libtool
-depends_lib         port:libiconv
-depends_run         port:fuse4x-kext
-
-livecheck.type      regex
-livecheck.url       ${homepage}
-livecheck.regex     {Fuse4X-([0-9.]+).dmg}
</del></span></pre></div>
<a id="trunkdportsfusefuse4xframeworkPortfile"></a>
<div class="modfile"><h4>Modified: trunk/dports/fuse/fuse4x-framework/Portfile (119124 => 119125)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/dports/fuse/fuse4x-framework/Portfile        2014-04-17 22:22:49 UTC (rev 119124)
+++ trunk/dports/fuse/fuse4x-framework/Portfile        2014-04-17 22:29:01 UTC (rev 119125)
</span><span class="lines">@@ -4,50 +4,12 @@
</span><span class="cx"> PortSystem          1.0
</span><span class="cx"> PortGroup           xcode 1.0
</span><span class="cx"> 
</span><ins>+replaced_by         osxfuse
+PortGroup           obsolete 1.0
+
</ins><span class="cx"> name                fuse4x-framework
</span><span class="cx"> version             0.9.2
</span><del>-set tag             [string map {. _ } $version]
</del><ins>+revision            1
</ins><span class="cx"> categories          fuse devel
</span><span class="cx"> platforms           macosx
</span><span class="cx"> maintainers         dports
</span><del>-description         Objective-C framework for Fuse4X
-
-long_description    Fuse4X implements a mechanism that makes it          \
-                    possible to implement a fully functional file        \
-                    system in a user-space program on Mac OS X. It       \
-                    aims to be API-compliant with the FUSE               \
-                    (File-system in USErspace) mechanism that            \
-                    originated on Linux.  Therefore, many existing       \
-                    FUSE file systems become readily usable on Mac OS    \
-                    X. This port provides a framework for writing        \
-                    file systems in Objective-C.
-
-homepage            http://fuse4x.github.io/
-license             BSD
-master_sites        https://github.com/fuse4x/framework/tarball/fuse4x_${tag}
-
-checksums           sha256  d2fff85dcf150da1e2693689f0497e2918c4a7abb266f86f06148fe2af013782 \
-                    rmd160  13b18364e0be9cae34e3f765a7aacc3b895ca167
-
-extract.mkdir       yes
-extract.post_args   &quot;| tar --strip-components=1 -xf -&quot;
-
-depends_lib         port:fuse4x
-
-post-patch {
-    reinplace &quot;s|-lfuse4x|-lfuse|&quot; ${worksrcpath}/framework.xcodeproj/project.pbxproj
-}
-
-xcode.configuration Release
-xcode.build.settings    LIBRARY_SEARCH_PATHS='${prefix}/lib' \
-                        HEADER_SEARCH_PATHS='${prefix}/include'
-
-destroot {
-    xinstall -d ${destroot}/${frameworks_dir}
-    file copy ${worksrcpath}/build/${xcode.configuration}/Fuse4X.framework \
-              ${destroot}/${frameworks_dir}
-}
-
-livecheck.type      regex
-livecheck.url       ${homepage}
-livecheck.regex     {Fuse4X-([0-9.]+).dmg}
</del></span></pre></div>
<a id="trunkdportsfusefuse4xkextPortfile"></a>
<div class="modfile"><h4>Modified: trunk/dports/fuse/fuse4x-kext/Portfile (119124 => 119125)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/dports/fuse/fuse4x-kext/Portfile        2014-04-17 22:22:49 UTC (rev 119124)
+++ trunk/dports/fuse/fuse4x-kext/Portfile        2014-04-17 22:29:01 UTC (rev 119125)
</span><span class="lines">@@ -2,119 +2,13 @@
</span><span class="cx"> # $Id$
</span><span class="cx"> 
</span><span class="cx"> PortSystem          1.0
</span><del>-PortGroup           xcode 1.0
</del><span class="cx"> 
</span><ins>+replaced_by         osxfuse
+PortGroup           obsolete 1.0
+
</ins><span class="cx"> name                fuse4x-kext
</span><span class="cx"> version             0.9.2
</span><del>-set tag             [string map {. _ } $version]
</del><ins>+revision            1
</ins><span class="cx"> categories          fuse devel
</span><span class="cx"> platforms           macosx
</span><span class="cx"> maintainers         dports
</span><del>-description         A kernel extension for Fuse4X
-
-long_description    Fuse4X implements a mechanism that makes it          \
-                    possible to implement a fully functional file        \
-                    system in a user-space program on Mac OS X. It       \
-                    aims to be API-compliant with the FUSE               \
-                    (File-system in USErspace) mechanism that            \
-                    originated on Linux.  Therefore, many existing       \
-                    FUSE file systems become readily usable on Mac OS    \
-                    X. This port provides the dynamically loadable       \
-                    kernel extension at the core of Fuse4X.
-
-homepage            http://fuse4x.github.io/
-license             BSD
-master_sites        https://github.com/fuse4x/kext/tarball/fuse4x_${tag}
-
-checksums           sha256  6755c61582667dfcb544ebe9b3b8292b18c235a9bdfa99e7d1081da9ed8c78d4 \
-                    rmd160  543a548e0a90f9bee3a77adcc7ca4eadebf6b596
-
-extract.mkdir       yes
-extract.post_args   &quot;| tar --strip-components=1 -xf -&quot;
-
-# This port installs a kernel module, so it must be built for the same
-# architecture as the kernel. We don't have a way to get that;
-# build_arch is the userland architecture, which may be different
-# (e.g. 64-bit userland with 32-bit kernel). So build a universal
-# binary by default on Intel platforms. On PPC, there's only one
-# kernel, so don't try to build it ppc64 or universal.
-supported_archs     i386 x86_64 ppc
-if {${build_arch} eq &quot;i386&quot; || ${build_arch} eq &quot;x86_64&quot;} {
-    default_variants    +universal
-}
-
-# kext destination: kext will be installed into ${kextdir}/fuse4x.kext.
-#
-# The kext is autoloaded by the library using load_fuse4x, so it
-# doesn't have to go into /System/Library/Extensions. It doesn't
-# matter where we put it, as long as it's kept in sync with the library.
-#
-# If updating the patchfile or ${kextdir}, must also update the
-# corresponding patch in the fuse4x port!
-patchfiles          patch-common_fuse_param.h.diff
-set kextdir        &quot;${prefix}/Library/Extensions&quot;
-post-patch {
-    reinplace &quot;s|@@KEXTPATH@@|${kextdir}/fuse4x.kext|&quot; ${worksrcpath}/common/fuse_param.h
-}
-
-xcode.configuration Release
-
-destroot.asroot     yes
-
-destroot {
-    xinstall -d ${destroot}${kextdir}
-    file copy ${worksrcpath}/build/${xcode.configuration}/fuse4x.kext ${destroot}${kextdir}
-    file attributes ${destroot}${kextdir}/fuse4x.kext -owner root -group wheel -permissions rwxr-xr-x
-
-    xinstall -d ${destroot}${kextdir}/fuse4x.kext/Support
-    xinstall -o root -m 4755 ${worksrcpath}/build/${xcode.configuration}/load_fuse4x ${destroot}${kextdir}/fuse4x.kext/Support
-}
-
-
-variant trace description {Enable debug logging: logs all filesystem operations} {
-    xcode.build.settings GCC_PREPROCESSOR_DEFINITIONS='FUSE4X_COUNT_MEMORY FUSE4X_DEBUG FUSE4X_TRACE_LK FUSE4X_TRACE_MSLEEP FUSE4X_TRACE_OP FUSE4X_TRACE_VNCACHE FUSE4X_SERIALIZE_LOGGING'
-}
-
-# We don't need to load the kext, because the fuse4x library will
-# autoload it when needed. However, if there's an existing version
-# loaded, we'd better unload it because it might be a different
-# version.
-#
-# Thus, check whether the kext is already loaded, and if so attempt to
-# unload it. If that fails, the user probably needs to unmount some
-# running filesystems; print a list.
-#
-# We do this both after deactivating an existing version (because the
-# user might be removing the port) and after activating a new version
-# (because the user might be upgrading from an installation that
-# didn't unload the kext).
-proc try_unload_kext {} {
-    set kextid &quot;org.fuse4x.kext.fuse4x&quot;
-    if {[string length [exec /usr/sbin/kextstat -lb $kextid]] &gt; 0} {
-        ui_msg &quot;The Fuse4X kernel extension is already loaded. Attempting to unload it.&quot;
-        if {![catch {exec /sbin/kextunload -b $kextid}]} {
-            ui_msg &quot;Successfully unloaded the previous installation of Fuse4X&quot;
-        } else {
-            set mounted [exec /sbin/mount -t fuse4x]
-            ui_warn &quot;Unable to unload the existing Fuse4X kernel extension.&quot;
-            ui_warn &quot;Please unmount the following filesystems, and then run &quot;
-            ui_warn &quot;`sudo kextunload -b $kextid`:&quot;
-            foreach line [split $mounted &quot;\n&quot;] {
-                regexp {on (/.*) \(fuse4x} $line -&gt; mountpoint
-                ui_warn &quot;  * $mountpoint&quot;
-            }
-        }
-    }
-}
-
-post-activate {
-    try_unload_kext
-}
-
-post-deactivate {
-    try_unload_kext
-}
-
-livecheck.type      regex
-livecheck.url       ${homepage}
-livecheck.regex     {Fuse4X-([0-9.]+).dmg}
</del></span></pre></div>
<a id="trunkdportsfuseosxfusePortfile"></a>
<div class="modfile"><h4>Modified: trunk/dports/fuse/osxfuse/Portfile (119124 => 119125)</h4>
<pre class="diff"><span>
<span class="info">--- trunk/dports/fuse/osxfuse/Portfile        2014-04-17 22:22:49 UTC (rev 119124)
+++ trunk/dports/fuse/osxfuse/Portfile        2014-04-17 22:29:01 UTC (rev 119125)
</span><span class="lines">@@ -4,7 +4,6 @@
</span><span class="cx"> PortSystem          1.0
</span><span class="cx"> 
</span><span class="cx"> name                osxfuse
</span><del>-conflicts           fuse4x
</del><span class="cx"> version             2.6.4
</span><span class="cx"> categories          fuse devel
</span><span class="cx"> platforms           macosx
</span></span></pre>
</div>
</div>

</body>
</html>