remove contrib/fuse #1409

Closed
opened 2011-05-24 18:20:37 +00:00 by zooko · 5 comments

I'm going to remove contrib/fuse because they are unsupported, bit-rotting, and help propagate the belief that Tahoe-LAFS doesn't have real FUSE support (which it actually does, by SFTP).

I'm going to remove contrib/fuse because they are unsupported, bit-rotting, and help propagate the belief that Tahoe-LAFS doesn't have real FUSE support (which it actually does, by SFTP).
zooko added the
contrib
minor
enhancement
1.8.2
labels 2011-05-24 18:20:37 +00:00
zooko added this to the 1.9.0 milestone 2011-05-24 18:20:37 +00:00
zooko self-assigned this 2011-05-24 23:59:51 +00:00
Author

The immediate cause of bitrot is that we are removing support for old-style config files (#1385), and some of the contrib/fuse modules use that config file format. The real problem though is that they don't have unit tests so there is no easy way to be sure that any change I make to them doesn't break them, or to know if they are already broken. Also, as mentioned, there is a fully-supported alternative now in the form of the SFTP server.

That said, there might be advantages to one of these approaches as compared to the SFTP server approach. (Certainly one advantage would be that you don't require a separate tool, the way the SFTP server requires sshfs, to get FUSE integration.)

So, if anyone is interested in maintaining and updating these tools, please adopt them and move them into a new source tree and let us know.

The immediate cause of bitrot is that we are removing support for old-style config files (#1385), and some of the contrib/fuse modules use that config file format. The real problem though is that they don't have unit tests so there is no easy way to be sure that any change I make to them doesn't break them, or to know if they are already broken. Also, as mentioned, there is a fully-supported alternative now in the form of the SFTP server. That said, there might be advantages to one of these approaches as compared to the SFTP server approach. (Certainly one advantage would be that you don't require a separate tool, the way the SFTP server requires sshfs, to get FUSE integration.) So, if anyone is interested in maintaining and updating these tools, please adopt them and move them into a new source tree and let us know.
Author

Attachment remove-contrib.darcs.patch (221953 bytes) added

**Attachment** remove-contrib.darcs.patch (221953 bytes) added
Author

nejucomo: please review remove-contrib.darcs.patch . Thank you!

nejucomo: please review [remove-contrib.darcs.patch](/tahoe-lafs/trac-2024-07-25/attachments/000078ac-6263-4625-ada7-8a28419d05a8) . Thank you!
zooko removed their assignment 2011-06-22 23:02:25 +00:00
nejucomo was assigned by zooko 2011-06-22 23:02:25 +00:00
marlowe commented 2011-07-12 12:50:49 +00:00
Owner

Reviewed the patch and it looks good to me. nejucomo, let me know if you want me to update the ticket as reviewed.

Reviewed the patch and it looks good to me. nejucomo, let me know if you want me to update the ticket as reviewed.
zooko@zooko.com commented 2011-07-12 15:31:33 +00:00
Owner

In changeset:4f8e3e5ae8fefc01:

contrib: remove the contributed fuse modules and the entire contrib/ directory, which is now empty
Also remove a couple of vestigial references to figleaf, which is long gone.
fixes #1409 (remove contrib/fuse)
In changeset:4f8e3e5ae8fefc01: ``` contrib: remove the contributed fuse modules and the entire contrib/ directory, which is now empty Also remove a couple of vestigial references to figleaf, which is long gone. fixes #1409 (remove contrib/fuse) ```
tahoe-lafs added the
fixed
label 2011-07-12 15:31:33 +00:00
zooko@zooko.com closed this issue 2011-07-12 15:31:33 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1409
No description provided.