[tahoe-dev] help! how do I manage dependencies on JavaScript code?

[Chris Palmer]

Zooko O'Whielacronx writes:

> Can you be more specific?

The WUI, SFTP, this visualization thing. Whatever causes the standalone
download package to still not build on FreeBSD. (I stopped trying.)

> top of my head that is bundled into Tahoe-LAFS and could be unbundled

So, so much could be unbundled. It's a filesystem. NFS has no PyCrypto
dependency, Samba has no darcs dependency...

> I don't think it is a good idea to make SFTP support unbundled or optional
> though, since it the source code for it is intertwined with all the other
> Tahoe-LAFS source code and

And you're making my case. The SFTP code should not exist. Tahoe-LAFS should
be a FUSE filesystem. Once you have that, you get everything else for free,
because all programs in the world ever know how to use filesystems.

> (or actually FUSE support was a very widely requested feature

Think about why.

> and you can set up FUSE by using sshfs with the Tahoe-LAFS SFTP server).

You can also tunnel HTTPS in GPG-encrypted email, but you don't. That is
backwards. You make a FUSE filesystem, mount it, and if for some reason you
want to unnecessarily access it via SFTP instead of using it as the
distributed filesystem it is, you use sftp(1) like normal.