On Oct 31, 1:13 pm, "Bill Hart" <[EMAIL PROTECTED]> wrote: > Thanks for your comments user923005. You can use GPL code in a > commercial environment. You just can't distribute it with and make it > a part of a commercial product. So you can use it for work, you just > can't sell it. That's fair enough in my view. If I write the code for > free, I can't see why others ought to be able to sell it unless > something is given back. > > Currently all of MPIR is LGPL by the way, though our intention is to > have LGPL and GPL versions eventually. Some of our code we definitely > want to remain GPL. This is because a number of mathematical software > companies have not given code back to the open source community but > used LGPL mathematical software in their code.
If they improve the LGPL portion of it, then they are breaking the law not to return their improvements. > The GPL only code will > essentially consist of our competitive advantage against those > companies. > > I don't know your background or about the company you work for (is it > Connx?). Yes, I work for CONNX. > Perhaps some details of the context in which you would like > to use the project for work may help us to understand better and may > help us with formulating our licensing policy. Naturally I'd be happy > to discuss it with you off list too if you'd prefer. Some sorts of things that are very useful for database work include statistical functions, random functions, etc. I plan to incorporate quantlib at some point: http://sourceforge.net/projects/quantlib/ Look here: http://www.connx.com/products/connx/CONNX%2010.5%20SP4%20UserGuide/connxcdd32.htm For instance, and open chapter 11, then examine the various functions that are available. SQL Statistical functions are probably the most interesting from a mathematical standpoint. We perform all of our mathematics using ~100 digits of precision (sounds like overkill but our customers can be scientists, astronomers, etc.) It's none of my business what license policy you choose. I am just saying that GPLv3 will mean that it won't get used commercially. If that is your goal, then it is perfectly fine. It all depends on what you want to happen with the tool set in the long run. I lament that some excellent software cannot be used for some interesting tasks because of the license policy. But I can always find another implementation or write my own. And there are people who have a fundamental philosophical bent that a certain way of doing things is the right way to do it. I have no problem with any sort of methods people choose to do things. Especially with open source software, there is more than one way to skin a cat, and one way or another we can usually find a way to solve the problems that need solving. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en -~----------~----~----~----~------~----~------~--~---
