From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] cygfuse
Date: Thu, 10 Mar 2022 21:53:34 +0100 [thread overview]
Message-ID: <ef9a7b5a-9a49-b8f9-588e-7d897b509d74@gmail.com> (raw)
In-Reply-To: <Pine.BSF.4.63.2109062038450.51672@m0.truegem.net>
On 10.03.2022 07:16, Mark Geisert wrote:
> This is a Cygwin version of libfuse{,3} that can be found in various
> Linux distributions. It is a couple of link libraries and additions to
> /usr/include to allow porting of FUSE apps. FUSE: File System In User
> Space. I will shortly be providing an sshfs FUSE app, to be covered by
> a separate ITP.
>
> Importantly, cygfuse depends on an underlying Windows FUSE
> implementation: WinFSP. In fact the Cygwin library code was provided by
> the author of WinFSP. I'm just providing a bona-fide Cygwin package for
> the code.
>
> WinFSP, and thus cygfuse, is made available under GPLv3 for Free/Libre
> and Open Source Software or under a commercial license.
>
> If another Windows FUSE provider shows interest in supporting Cygwin, I
> suspect it could be supported with alternatives(8).
>
> The initial project files for review are located at:
> http://maxrnd.com/~mark/cygwin/cygfuse/cygfuse.cygport
> http://maxrnd.com/~mark/cygwin/cygfuse/cygfuse-3.2.0-1-src.tar.xz
> http://maxrnd.com/~mark/cygwin/cygfuse/cygfuse-3.2.0-1.src.patch
>
> Thanks for reading and for any feedback you might have,
>
> ..mark
added to the cygwin-pkg-maint list
Thanks
Marco
next prev parent reply other threads:[~2022-03-10 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 6:16 Mark Geisert
2022-03-10 20:53 ` Marco Atzeri [this message]
2022-03-12 14:43 ` Jon Turney
2022-03-12 14:46 ` Jon Turney
2022-03-25 8:24 ` Mark Geisert
2022-03-27 8:20 ` [ITP] cygfuse -- cygport issues solved Mark Geisert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ef9a7b5a-9a49-b8f9-588e-7d897b509d74@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).