[Mono-dev] Announce: Mono.Fuse (+ Required Mono.Posix Changes)

Jonathan Pryor jonpryor at vt.edu
Thu Aug 31 08:13:35 EDT 2006

On Thu, 2006-08-31 at 06:43 -0400, Jonathan Pryor wrote:
> On Thu, 2006-08-31 at 07:27 +0200, pablosantosluac wrote:
> > So, let's say I want to develop a filesystem to be integrated with our 
> > software: should I use SULF or should I wait for Mono.Fuse?
> So you basically have four choices:
> 1. Use Sulf, even though it's been abandoned (it's darcs repo is
> inaccessible, so you'd have to go with the previous 0.3 tarball).
> (Furthermore, I've had no luck building & installing the 0.3 tarball,
> but your mileage may vary.)
> 2. Use fusewrapper's low-level C# interface.
> 3. Use Nemerle and fusewrapper's high-level Sulf interface.
> 4. Wait for Mono.Fuse.  (Actually, you'd be waiting for the Mono.Fuse
> dependencies within Mono.Posix to be committed, then either use svn-HEAD
> or wait for 1.1.18 to use a separate Mono.Fuse tarball.  Furthermore, I
> have no idea when the Mono.Posix dependencies will get committed; it
> depends on when I get approval, which may require changes...)

And a 5th option: If you need a solution *now*, you can fork Mono.Fuse
and MonoPosixHelper.  Copy the required MonoPosixHelper type
declarations and conversion functions into MonoFuseHelper (e.g.
Mono_Posix_ToStat, Mono_Posix_FromStat, Mono_Posix_ToFilePermissions,
etc.), and build your own copy of MonoFuseHelper.

This would work, and can be done now, it's just not terribly elegant
(nor long-term safe, if e.g. a Mono.Unix.Native structure needs to
change your copied functions will be out-of-sync).

 - Jon

More information about the Mono-devel-list mailing list