On Mar 17, 2007, at 1:36 PM, Giovanni wrote: > I know we have visited this before, but I would like some clarity as I > see how much of apple OSX relies on open source technologies.
If you include "any" GPL code within your application - your application becomes licensed under the GPL. It really IS that simple. If you dig into Apple's open source code, you'll you find very distinct lines between GPL and non-GPL code. > The question is basically how can you integrate GPL'ed apps with > commercial apps without having to release your source or open your > application? The GPL code that you are calling MUST be in a self-contained binary that your application calls. This way, your application is not dependent on the GPL code, but rather the output or reult of the execution of that GPL code. This way, if a user yells about the source being required, all you need to do it share the GPL project's code, you don't need to share YOUR project's code. For libraries like GLIBC, you'll find that they are mostly release under the LGPL (Lesser GPL). As one additional benefit to this type of design, when you come up with a non-GPL way to achieve the GPL code's results, it's as simple as changing the call in your project and you are now totally GPL-free. Also, if the code is really important to your situation, you can always contact the GPL code's author and request a special release under a less restrictive, open source license such as BSD, MPL, QPL, et al. HTH, Tim -- Tim Jones [EMAIL PROTECTED] _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
