Board index » delphi » Re: GNU

Re: GNU


2005-05-10 11:37:01 AM
delphi209
Craig Stuntz [TeamB] writes:
Quote
As I already said, that is incorrect if you follow the recommendation
in the FAQ:
www.gnu.org/licenses/gpl-faq.html
"If you want your program to link against a library not covered by that
exception, you need to add your own exception, wholly outside of the
GPL. This copyright notice and license notice give permission to link
The above is is true, but only the authors of the library/components
can grant this exception, not the users of the library/components. So,
you would have to contact ALL of the copyright holders of the
third-party source and convince them to modify their license just for
you. This isn't easy to do, especially with older projects where
authors might have changed email addresses, passed away, moved on, etc.
In that case, you can never relicense the code with exceptions, unless
they had that provision in the original license.
Quote:
"if you want to use parts of other GPL-covered programs by other authors
in your code, you cannot authorize the exception for them. You have to
get the approval of the copyright holders of those programs."
Erik
 
 

Re: GNU

Jason Southwell writes:
Quote
Not really, but close. It forbids you from closing the source if an
external entity uses the binary. Regardless if you are making a buck
I don't see any exceptions for distribution to co-workers. Where do
you see this in the license?
Erik
 

Re: GNU

K. Sallee writes:
Quote
The exception to this rule occurs either if the library is LGPLed or if
the author of the GPLed software includes permission to do so under a
controlled interface. A propriatory component can't give permission
to be included with GPL software and stay propriatory.
...unless you consider dual-licensing of the code to be both proprietary
and free software at the same time.
Erik
 

Re: GNU

Ben Hochstrasser writes:
Quote
Wrong. That would make GPLed Delphi applications impossible (because you
still require commercial code (Delphi with the compiler and all the
components that come with it)) to use it.
The GPL only covers the software you create. It does not prevent
using Delphi or VS to compile code, just as it allows one to use a
commercial text editor to create a GPL application. The restriction is
that you need to be sure linked-in libraries are either GPL-compatible
(Borland released a GPL RTL/VCL with Kylix) or are part of the exception
granted in the license that exempts libraries "normally distributed (in
either source or binary form) with the major components (compiler,
kernel, and so on) of the operating system on which the executable
runs." It would be up to the FSF and the lawyers to determine, for
example, if the Delphi 7 RTL/VCL libraries are covered by the exception,
but I kind of doubt it because they are not distributed as part "of the
operating system" (the Windows OS does not include any Borland libraries).
Erik
 

Re: GNU

Quote
...unless you consider dual-licensing ofthe code to be both proprietary and freesoftware at the same time.
True. And another very practical solution if the author is willing to do so.
Kevin
--
Software for resource managers and researchers
www.ecostats.com