setup: remove a convenience copy of figleaf, to ease inclusion into Ubuntu Karmic...
authorZooko O'Whielacronx <zooko@zooko.com>
Thu, 24 Sep 2009 05:32:15 +0000 (22:32 -0700)
committerZooko O'Whielacronx <zooko@zooko.com>
Thu, 24 Sep 2009 05:32:15 +0000 (22:32 -0700)
commitaaaa633f189adba42646edc12c93a4d4c52f4373
tree731a61b8cc54f975ca55ee3f310d43dd2e7a4cd6
parentabdf8a6f10fa8dda9f2af47b97fd0fe5cf630454
setup: remove a convenience copy of figleaf, to ease inclusion into Ubuntu Karmic Koala
We need to carefully document the licence of figleaf in order to get Tahoe-LAFS into Ubuntu Karmic Koala.  However, figleaf isn't really a part of Tahoe-LAFS per se -- this is just a "convenience copy" of a development tool.  The quickest way to make Tahoe-LAFS acceptable for Karmic then, is to remove figleaf from the Tahoe-LAFS tarball itself.  People who want to run figleaf on Tahoe-LAFS (as everyone should want) can install figleaf themselves.  I haven't tested this -- there may be incompatibilities between upstream figleaf and the copy that we had here...
misc/figleaf2el.py
misc/figleaf2html [deleted file]
src/allmydata/test/trial_figleaf.py
src/allmydata/util/figleaf.py [deleted file]
src/allmydata/util/figleaf_htmlizer.py [deleted file]