I'd rather not have to download a bunch of filesystems I don't use as part of a FUSE distribution.. That also causes problems with release schedules -- what if there is a problem that warrants a new release of a contributed filesystem? Should that force a new release of FUSE? I think that would be more trouble then it's worth.
On Sat, 2004-03-20 at 11:41, Michael Still wrote:
I've been working on a FUSE filesystem, which I released the first
version of the other day
(http://lists.samba.org/archive/linux/2004-March/010211.html). In order
for people to use the filesystem they need to have FUSE. I am therefore
wondering what people's opinions of creating a contrib/ directory in the
FUSE distribution for contributed filesystems?
The files I've released are a CVS snapshot of my work on the filesystem,
and therefore include the FUSE files. I'm happy to distribute the
filesystem without FUSE, it's just more of a hassle for users.