- removed relative path for jython.jar, replaced with a def
which developer must edit
Added README
- overviews the i2psam.jar building process
Added build.bat
- an attempt at a build script which might work on Windows, for people
who don't have 'make' installed
developers to use the software in a particular way (to have the software display
"Copyright \xa91996-1999 Corporation for National Research Initiatives; All Rights Reserved")
section 3 has a similar problem.
this violates the rule #2 of the i2p license policy -
All software bundled in the I2P distributions will allow
2) use with no restrictions on how, when, where, why, or by whom is running it
in addition, using jython does not seem wise for some situations, as the license is
not GPL compatible (aka cannot be used with the GPL'ed SAM code)
sorry for the confusion earlier aum, I had mistakenly seen a COPYING file and
assumed it was Yet Another copy of the GPL.
http://lists.debian.org/debian-python/2001/debian-python-200107/msg00001.html as
well.
client sources in a dissected XML form.
If you're working on I2P SAM, we strongly encourage you to install
the Leo editor (http://leo.sf.net), and use it to edit the
sources. Otherwise, we're stuck with the menial task of re-importing
your changes into the Leo tree. Thanks for your understanding and
co-operation.
I2P via SAM. File contains a demo function, which both tests
the library, and shows simple examples of how to use the API.
Run epydoc on this file to get good doco.
likely that two or more I2P facilities will need it.
This seems a more acceptable alternative than hard-linking
jython.jar code into each app using it (which would result
in bloatage).
