Tahoe-LAFS requires a package named "zope.interface". You may be able
  to install that package using the operating system's package manager,
  or from the Python Package Index ¹, or you could download a
  "tahoe-deps" tarball from tahoe-lafs.org ², which includes
  zope.interface as well as all other packages that Tahoe-LAFS needs. If
  you get the "SUMO" release from the Tahoe-LAFS releases ³, then that
  comes with a copy of the tahoe-deps packages already in place.

Or, you could use pkgsrc (pkgsrc.org); after you have built tahoe and
dependencies on a system, you can install them on a machine with the
same os/arch.  Or, you can run a command (make fetch-list) on the
non-connected machine to get a shell script that will grab all the
needed tarballs, bring the script out, download, and bring the bits in,
and then build.  The pkgsrc process goes to some effort to avoid
downloading things during package build other than via the download
process above.   This may be harder than what you want to get into, but
it's a general approach to disconnected machines.

Attachment: pgpAABYDeWqcA.pgp
Description: PGP signature

_______________________________________________
tahoe-dev mailing list
[email protected]
http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev

Reply via email to