[tahoe-dev] Getting Tahoe into Debian (was: Re: linking pycryptopp against system provided cryptopp)

[Brian Warner]

> I'm going to chime in here to express a general desire that Tahoe, as
> packaged for general distribution, not deploy a node that connects to the
> production grid and advertises storage.

Yeah. I think we should make two packages:

 "tahoe": this just provides the /usr/bin/tahoe command, and the libraries
          that it needs. This one could go into Debian. It does *not* create
          a node upon install.

 "allmydata-client": this Depends on "tahoe", probably would *not* go into
                     Debian (instead we'd distribute it from the
                     allmydata.org or allmydata.com APT repository), and
                     *would* create a node at install time (in
                     /var/run/allmydata-client or something), attached as a
                     non-storage client to the allmydata.com production grid.
                     We'd point our Linux-using customers at this, and give
                     them an easy way to get the allmydata.com credentials
                     into it.


I had somewhat similar issues with Buildbot, where the debian package
provides both the /usr/bin/buildbot tool and also tries to set up an
environment (a 'buildbot' account, and a /var/something working directory)
for a buildbot master or slave to live in (which I never use). I'd be happier
to leave the latter part out of the "tahoe" package.

cheers,
 -Brian