[tahoe-dev] moving to Git!

[Brian Warner]

On 1/5/12 9:35 AM, Greg Troxel wrote:

> Agreed (although with pkgsrc I think you can build everything
> unprivileged in a path in your homedir, but that fails the "too much
> hassle" test). I didn't mean to say I thought the SUMO build shouldn't
> exist. Just that it seems like the included bits don't really belong
> in tahoe vcs.

Yeah, that's what I'm thinking too. The setup.py code can look for a
tahoe-deps/ directory, but the normal source tree won't ever have
anything in there. The SUMO tarball can be constructed (with a script)
to pre-populate that directory with tarballs that you'd otherwise need
to download separately, without letting the version-control system know
about them.

The intention of the SUMO tarball was to make it easy to get everything
you needed from a single place, say because you were getting on a plane,
or scp'ing files to secure remote box that's locked-down and not allowed
to make arbitrary outbound network connections. There's gotta be a
baseline, though ("you need: python, gcc, libopenssl, tahoe-SUMO"),
which is frequently a hassle to express.

cheers,
 -Brian