On Saturday 01 September 2007 11:20, Eric Bollengier wrote: > Hello, > > > Now that Bacula 2.2.1 is release (currently uploading), I've begun work > > on a project to liberate Bacula from what I consider "onerous" > > restrictions of the GPL. The FSF considers the OpenSSL license onerous, > > so forbids mixing GPL and OpenSSL code, which IMO is a pity since it > > inhibits the synergy of using Open Source code. > > It's true, choosing a good library is very difficult, and it is paintful to > have to drop it after many years... :( > > What you want to use instead of OpenSSL ? Something like Gnu TLS ?
Well, I'm attacking the problem from the other end. Though I would like to see Bacula support GnuTLS and probably NSS, those are *big* projects. The idea is that once I rid Bacula of any third party GPL copyrighted code (only two files left ...) then we can either modify our GPL license to permit interoperation with any OSI defined Open Source code, or we can create a new license (highly frowned on by the Open Source community), or we can simply choose a different less restrictive *Open Source* license -- note I stressed Open Source. Bacula is Open Source and will remain so, and any new license will be Open Source, with no more restrictions (and probably less) than are currently imposed by the GPL. The most conservative path is to modify the GPL that Bacula currently uses, then to calmly consider other Open Source Licenses. First though, there is unfortunately, some non-productive rewriting necessary. ==== If you are interested in helping, one of the files that needs to be replaced is src/lib/fnmatch.c. Along with it are fnmatch.h, enh_fnmatch.c, and enh_fnmatch.h. enh_fnmatch.c is simply a derivative of fnmatch.c that has some enhancements that Robert added. We have made a few minor changes to fnmatch.c to support Win32 paths. There are two ways that I see to eliminate the FSF fnmatch.c. One is to take the current system fnmatch.c (either Linux or FreeBSD) and modify it to have our Win32 path code. Another possibility is write a new fnmatch.c that uses your code to convert a wildcard to a regex and then call our regex routine. The advantage of using the Linux fnmatch.c (LGPL license) is that it uses wchar, which gives us a functionality that is currently missing from our fnmatch.c Once fnmatch.c is converted, the task will be to separate out the enhancements that were added to enh_fnmatch.c and to either add them to our new fnmatch.c or create a new enh_fnmatch.c For the moment, I am working on rewriting src/findlib/makepath.c Best regards, Kern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
