From: Jon Turney <jon.turney@dronecode.org.uk>
To: Mark Geisert <mark@maxrnd.com>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] cygfuse
Date: Sat, 12 Mar 2022 14:46:17 +0000 [thread overview]
Message-ID: <23cd727e-910f-7eff-7bc2-e763c0aa2627@dronecode.org.uk> (raw)
In-Reply-To: <10fcc7c4-0822-0dd8-527e-e46e79e2f031@dronecode.org.uk>
On 12/03/2022 14:43, Jon Turney wrote:
> On 10/03/2022 06: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).
Oops. This email escaped early...
> It's not quite that straightforward as the Windows loader can only
> follow symlinks to DLLs if they are
... made using 'winsymlinks:native'
> But that's not
... important right now.
next prev parent reply other threads:[~2022-03-12 14:46 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
2022-03-12 14:43 ` Jon Turney
2022-03-12 14:46 ` Jon Turney [this message]
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=23cd727e-910f-7eff-7bc2-e763c0aa2627@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=mark@maxrnd.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).