Re: vcal commits
"Roger Binns" <[email protected]>
| Newsgroups | gmane.comp.mobile.bitpim.devel |
|---|---|
| Message-ID | <016a01c5081c$d8cae810$3501a8c0@rogersqyvr14d3> |
> I've been using cygwin cvs as the client and I'll look into the Windows one. cygwin does all sorts of stuff behind the scenes to try to ensure that files are in Windows format for Windows programs and Unix format for cygwin programs. > I've been checking files in and out and haven't noticed the problem, It won't screw up existing files since they already have the EOL set. It is only new files which presumably you are editing with a Windows EOL style editor. > I guess you've been correcting them behind the scence. Thanks :-) Yup :-) http://article.gmane.org/gmane.comp.mobile.bitpim.devel/1363 > And I thought GPL is GPL :-) It is. The original license I used for BitPim was the Artistic License. I didn't particularly care what people did, as long as they couldn't represent their versions as *the* BitPim. Anyway it turns out that the Artistic License has various holes in it, including allowing bug fixes. So is adding support for a new phone a bug fix? The GPL is a no-compromise license. Everything in the process needs to be GPL compatible (except parts of the operating system). At the time we switched to the GPL, I was also trying to use OpenSSL for BitFling. Because of the advertising clause in OpenSSL, the BitPim GPL had to have an exception to allow using OpenSSL. Later on it turned out impossible to use the M2Crypto OpenSSL wrapper and I switched to Paramiko and did it using SSH. Removing the OpenSSL exception would require everyone who has to code to agree (again). However we may need to use OpenSSL again in the future, and I think the (minimal) SSL support in the Python standard library uses OpenSSL. So it is prudent to just leave the exception in there. But that does mean we use the no-compromise GPL with the one compromise exception. That won't affect other code we use except for other GPL code since they have no compromises :-) > I'll use the vcard package instead. You'll probably want to split the vcard module into a vfile (generic) module and a vcard module and add the vcal module, or just dump all the vcal stuff in there anyway. > I'd like to do some more testing on it, so please back it out for this build. Ok. 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