[119125] trunk/dports/fuse
dports at macports.org
dports at macports.org
Thu Apr 17 15:29:01 PDT 2014
Revision: 119125
https://trac.macports.org/changeset/119125
Author: dports at macports.org
Date: 2014-04-17 15:29:01 -0700 (Thu, 17 Apr 2014)
Log Message:
-----------
fuse4x-*: replaced_by osxfuse (#39456)
Modified Paths:
--------------
trunk/dports/fuse/fuse4x/Portfile
trunk/dports/fuse/fuse4x-framework/Portfile
trunk/dports/fuse/fuse4x-kext/Portfile
trunk/dports/fuse/osxfuse/Portfile
Removed Paths:
-------------
trunk/dports/fuse/fuse4x/files/
trunk/dports/fuse/fuse4x-kext/files/
Modified: trunk/dports/fuse/fuse4x/Portfile
===================================================================
--- 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)
@@ -3,73 +3,12 @@
PortSystem 1.0
+replaced_by osxfuse
+PortGroup obsolete 1.0
+
name fuse4x
version 0.9.2
-revision 1
-set tag [string map {. _ } $version]
+revision 2
categories fuse devel
platforms macosx
maintainers dports
-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 "| tar --strip-components=1 -xf -"
-
-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 "${prefix}/Library/Extensions"
-post-patch {
- reinplace "s|@@KEXTPATH@@|${kextdir}/fuse4x.kext|" ${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 "s|-lfuse4x|-lfuse|" ${worksrcpath}/fuse.pc.in
- reinplace "s|libfuse4x|libfuse|g" ${worksrcpath}/lib/Makefile.am
- reinplace "s|libfuse4x.la|libfuse.la|" ${worksrcpath}/example/Makefile.am
-
- # automake 1.13 compatibility (see #37451)
- file mkdir ${worksrcpath}/m4
- reinplace "s|AM_CONFIG_HEADER|AC_CONFIG_HEADERS|" ${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}
Modified: trunk/dports/fuse/fuse4x-framework/Portfile
===================================================================
--- 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)
@@ -4,50 +4,12 @@
PortSystem 1.0
PortGroup xcode 1.0
+replaced_by osxfuse
+PortGroup obsolete 1.0
+
name fuse4x-framework
version 0.9.2
-set tag [string map {. _ } $version]
+revision 1
categories fuse devel
platforms macosx
maintainers dports
-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 "| tar --strip-components=1 -xf -"
-
-depends_lib port:fuse4x
-
-post-patch {
- reinplace "s|-lfuse4x|-lfuse|" ${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}
Modified: trunk/dports/fuse/fuse4x-kext/Portfile
===================================================================
--- 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)
@@ -2,119 +2,13 @@
# $Id$
PortSystem 1.0
-PortGroup xcode 1.0
+replaced_by osxfuse
+PortGroup obsolete 1.0
+
name fuse4x-kext
version 0.9.2
-set tag [string map {. _ } $version]
+revision 1
categories fuse devel
platforms macosx
maintainers dports
-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 "| tar --strip-components=1 -xf -"
-
-# 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 "i386" || ${build_arch} eq "x86_64"} {
- 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 "${prefix}/Library/Extensions"
-post-patch {
- reinplace "s|@@KEXTPATH@@|${kextdir}/fuse4x.kext|" ${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 "org.fuse4x.kext.fuse4x"
- if {[string length [exec /usr/sbin/kextstat -lb $kextid]] > 0} {
- ui_msg "The Fuse4X kernel extension is already loaded. Attempting to unload it."
- if {![catch {exec /sbin/kextunload -b $kextid}]} {
- ui_msg "Successfully unloaded the previous installation of Fuse4X"
- } else {
- set mounted [exec /sbin/mount -t fuse4x]
- ui_warn "Unable to unload the existing Fuse4X kernel extension."
- ui_warn "Please unmount the following filesystems, and then run "
- ui_warn "`sudo kextunload -b $kextid`:"
- foreach line [split $mounted "\n"] {
- regexp {on (/.*) \(fuse4x} $line -> mountpoint
- ui_warn " * $mountpoint"
- }
- }
- }
-}
-
-post-activate {
- try_unload_kext
-}
-
-post-deactivate {
- try_unload_kext
-}
-
-livecheck.type regex
-livecheck.url ${homepage}
-livecheck.regex {Fuse4X-([0-9.]+).dmg}
Modified: trunk/dports/fuse/osxfuse/Portfile
===================================================================
--- 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)
@@ -4,7 +4,6 @@
PortSystem 1.0
name osxfuse
-conflicts fuse4x
version 2.6.4
categories fuse devel
platforms macosx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-changes/attachments/20140417/eb6b9b99/attachment-0001.html>
More information about the macports-changes
mailing list