tahoe-lafs/windows
Zooko O'Whielacronx 923ba7db68 setup: remove binary WinFUSE modules
I would prefer to have just source code, or indications of what 3rd-party packages are required, under revision control, and have the build process generate o
r acquire the binaries as needed.  Also, having these in our release tarballs is interfering with getting Tahoe-LAFS uploaded into Ubuntu Karmic.  (Technicall
y, they would accept binary modules as long as they came with the accompanying source so that they could satisfy their obligations under GPL2+ and TGPPL1+, bu
t it is easier for now to remove the binaries from the source tree.)
In this case, the binaries are from the tahoe-w32-client project: http://allmydata.org/trac/tahoe-w32-client , from which you can also get the source.
2009-09-24 14:14:36 -07:00
..
amdicon.ico add confwiz to py2exe build 2008-01-11 18:42:27 -07:00
confwiz.py commenting out open_welcome_page argument that doesn't seem to work with real installer 2008-02-15 12:50:10 -07:00
depends.py fix windows build 2008-01-23 15:17:27 -07:00
installer.bmp windows installer: use an allmydata logo in setup wizard 2008-03-18 16:18:07 -07:00
installer.ico add windows installer target to build 2008-01-11 20:41:21 -07:00
installer.tmpl rollback change... move allmydatacontextmenu registration to installer.tmpl in tahoe-w32-client\installer 2008-11-03 15:36:47 -07:00
Makefile windows/Makefile: fix dependencies: windows-installer must cause windows-exe to run 2008-09-11 22:21:51 -07:00
setup.py further fixes to windows build (pkg_resources / web templates) 2008-01-23 18:52:43 -07:00
tahoe.py cleanup mac and windows build code 2008-01-23 21:06:41 -07:00
tahoesvc.py cleanup mac and windows build code 2008-01-23 21:06:41 -07:00