kpriv/pkgsrc-wip
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc-wip/fusefs-sshfs/Makefile

29 lines
687 B
Makefile
Raw Normal View History

Add pkg-config to USE_TOOLS and make bluez-libs include conditional on Linux
2009-07-10 21:49:37 +02:00
# $NetBSD: Makefile,v 1.7 2009/07/10 19:49:37 absd Exp $
* Initial import of fusefs-sshfs This is a filesystem client based on the SSH File Transfer Protocol. Since most SSH servers already support this protocol it is very easy to set up: i.e. on the server side there's nothing to do. On the client side mounting the filesystem is as easy as logging into the server with ssh. The idea of sshfs was taken from the SSHFS filesystem distributed with LUFS, which I found very useful. There were some limitations of that codebase, so I rewrote it. Features of this implementation are: - Based on FUSE (the best userspace filesystem framework for Linux ;) - Multithreading: more than one request can be on it's way to the server - Allowing large reads (max 64k) - Caching directory contents - Reconnect on failure
2006-02-12 04:04:43 +01:00
#
DISTNAME= sshfs-fuse-1.4
* fix PKGNAME.
2006-02-20 11:43:15 +01:00
PKGNAME= fuse-sshfs-1.4
Per the process outlined in revbump(1), perform a recursive revbump on packages that are affected by the switch from the openssl 0.9.7 branch to the 0.9.8 branch. ok jlam@
2008-01-18 05:30:10 +01:00
PKGREVISION= 1
Delint: - add or fix RCS ids - fix permission problems (USE_TOOLS etc.) - fix MESSAGE, DESCR, COMMENT problems - other minor tweaks (all reported by pkglint -Wall)
2006-10-29 12:23:06 +01:00
CATEGORIES= sysutils
* Initial import of fusefs-sshfs This is a filesystem client based on the SSH File Transfer Protocol. Since most SSH servers already support this protocol it is very easy to set up: i.e. on the server side there's nothing to do. On the client side mounting the filesystem is as easy as logging into the server with ssh. The idea of sshfs was taken from the SSHFS filesystem distributed with LUFS, which I found very useful. There were some limitations of that codebase, so I rewrote it. Features of this implementation are: - Based on FUSE (the best userspace filesystem framework for Linux ;) - Multithreading: more than one request can be on it's way to the server - Allowing large reads (max 64k) - Caching directory contents - Reconnect on failure
2006-02-12 04:04:43 +01:00
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=fuse/}
MAINTAINER= pancake@phreaker.net
Repair even more linkrot in MASTER_SITES and HOMEPAGEs...
2006-05-01 16:20:07 +02:00
HOMEPAGE= http://fuse.sourceforge.net/
* Initial import of fusefs-sshfs This is a filesystem client based on the SSH File Transfer Protocol. Since most SSH servers already support this protocol it is very easy to set up: i.e. on the server side there's nothing to do. On the client side mounting the filesystem is as easy as logging into the server with ssh. The idea of sshfs was taken from the SSHFS filesystem distributed with LUFS, which I found very useful. There were some limitations of that codebase, so I rewrote it. Features of this implementation are: - Based on FUSE (the best userspace filesystem framework for Linux ;) - Multithreading: more than one request can be on it's way to the server - Allowing large reads (max 64k) - Caching directory contents - Reconnect on failure
2006-02-12 04:04:43 +01:00
COMMENT= Mount remote directories using ssh and FUSE
Delint: - add or fix RCS ids - fix permission problems (USE_TOOLS etc.) - fix MESSAGE, DESCR, COMMENT problems - other minor tweaks (all reported by pkglint -Wall)
2006-10-29 12:23:06 +01:00
* Initial import of fusefs-sshfs This is a filesystem client based on the SSH File Transfer Protocol. Since most SSH servers already support this protocol it is very easy to set up: i.e. on the server side there's nothing to do. On the client side mounting the filesystem is as easy as logging into the server with ssh. The idea of sshfs was taken from the SSHFS filesystem distributed with LUFS, which I found very useful. There were some limitations of that codebase, so I rewrote it. Features of this implementation are: - Based on FUSE (the best userspace filesystem framework for Linux ;) - Multithreading: more than one request can be on it's way to the server - Allowing large reads (max 64k) - Caching directory contents - Reconnect on failure
2006-02-12 04:04:43 +01:00
GNU_CONFIGURE= YES
Add pkg-config to USE_TOOLS and make bluez-libs include conditional on Linux
2009-07-10 21:49:37 +02:00
USE_TOOLS+= gmake pkg-config
PKG_DESTDIR_SUPPORT= user-destdir
.include "../../mk/bsd.prefs.mk"
.if ${OPSYS} == "Linux"
.include "../../wip/bluez-libs/buildlink3.mk"
.endif
* Initial import of fusefs-sshfs This is a filesystem client based on the SSH File Transfer Protocol. Since most SSH servers already support this protocol it is very easy to set up: i.e. on the server side there's nothing to do. On the client side mounting the filesystem is as easy as logging into the server with ssh. The idea of sshfs was taken from the SSHFS filesystem distributed with LUFS, which I found very useful. There were some limitations of that codebase, so I rewrote it. Features of this implementation are: - Based on FUSE (the best userspace filesystem framework for Linux ;) - Multithreading: more than one request can be on it's way to the server - Allowing large reads (max 64k) - Caching directory contents - Reconnect on failure
2006-02-12 04:04:43 +01:00
.include "../../security/openssl/buildlink3.mk"
.include "../../devel/glib2/buildlink3.mk"
Use pkgsrc/mk/fuse.buildlink3.mk.
2007-03-07 18:38:11 +01:00
.include "../../mk/fuse.buildlink3.mk"
* Initial import of fusefs-sshfs This is a filesystem client based on the SSH File Transfer Protocol. Since most SSH servers already support this protocol it is very easy to set up: i.e. on the server side there's nothing to do. On the client side mounting the filesystem is as easy as logging into the server with ssh. The idea of sshfs was taken from the SSHFS filesystem distributed with LUFS, which I found very useful. There were some limitations of that codebase, so I rewrote it. Features of this implementation are: - Based on FUSE (the best userspace filesystem framework for Linux ;) - Multithreading: more than one request can be on it's way to the server - Allowing large reads (max 64k) - Caching directory contents - Reconnect on failure
2006-02-12 04:04:43 +01:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink