On Monday,2009-10-19, at 15:56 , Vanderlinden, Chris wrote: > Thank you for clearing that up, makes a lot more sense now. > > So the goal on my end seems to be as such: > > Install Python > Install all dependencies for tahoe > Install / build tahoe-lafs > > Deploy tahoe-lafs introducer + server nodes > > Build tahoe-w32-client (if so desired) > Test! > > (documenting along the way of course)
Awesome! I really appreciate your offer to post documentation about your progress. Updates and edits to these docs would be good: http://allmydata.org/trac/tahoe/wiki/InstallDetails http://allmydata.org/trac/tahoe/wiki/InstallOnWindows Building Tahoe-LAFS for Windows is definitely doable -- many people have done it, and we have a buildbot that runs the unit tests on Windows on every darcs commit (http://allmydata.org/buildbot/ ), but it isn't automatic right now, mostly because its dependencies pycryptopp and zfec seem not to be found by the build tool even though they are available from here: http://allmydata.org/source/tahoe/deps/tahoe-dep-eggs/ Regards, Zooko _______________________________________________ tahoe-dev mailing list [email protected] http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
