vcal commits

Joe,

There are a few issues with your commits.  Whatever CVS client you are 
using is not correctly dealing with end of lines.  It should be converting
the end of lines it sends to the CVS server to be UNIX/C style (ie
\n not \r\n or \r).  On Windows I use the command line cvs client
together with plink/pageant from Putty for the SSH stuff.  That
combination definitely gets things correct.  Let me know if you want
more details on how to get it working.

Also the license for vcal.py won't work with BitPim unless you get
permission from them.  The BitPim license is the GPL, but with an
exception allowing linking against OpenSSL.  For us to get stuff
from other parties, they also have to allow that OpenSSL linking
exception.  OpenSSL is actually GPL compliant, except for one
clause that requires mentioning stuff in your doc (aka an "advertising"
clause).  The main author of OpenSSL now works for Verisign and
to my knowledge won't retract the clause, so GPL projects have to
either not use OpenSSL or have the exception.

And then on top of that vcal.py isn't needed.  Use vcard.py which
already has all the parsing logic, and deals with all the issues
out there for how various programs don't format things exactly
correctly.  Examples of some issues are character set encoding 
for fields, encoding of the whole file, incorrectly doing continuations,
and many other things.

Let us know if you can fix this this evening.  If not, I'll disable
it for the build.

Roger


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl