The GPL is actually quite clear, if you add GPL code to your project your project should be GPL.
This is different for LGPL, but FGData and FGAddon are both GPL (which does not mean there could be LGPL'ed Nasal libraries in FGData or FGAddon).
Erik
erik wrote in Thu May 12, 2016 12:39 pm:The GPL is actually quite clear, if you add GPL code to your project your project should be GPL.
in many cases you can distribute the GPL-covered software alongside your proprietary system. To do this validly, you must make sure that the free and non-free programs communicate at arms length, that they are not combined in a way that would make them effectively a single program.
The difference between this and “incorporating” the GPL-covered software is partly a matter of substance and partly form. The substantive part is this: if the two programs are combined so that they become effectively two parts of one program, then you can't treat them as two separate programs. So the GPL has to cover the whole thing.
If the two programs remain well separated, like the compiler and the kernel, or like an editor and a shell, then you can treat them as two separate programs—but you have to do it properly. The issue is simply one of form: how you describe what you are doing. Why do we care about this? Because we want to make sure the users clearly understand the free status of the GPL-covered software in the collection.
If people were to distribute GPL-covered software calling it “part of” a system that users know is partly proprietary, users might be uncertain of their rights regarding the GPL-covered software. But if they know that what they have received is a free program plus another program, side by side, their rights will be clear.
Hooray wrote in Thu May 12, 2016 12:48 pm:erik wrote in Thu May 12, 2016 12:39 pm:The GPL is actually quite clear, if you add GPL code to your project your project should be GPL.
Sorry, that's wrong, or at least fairly inaccurate: it solely depends on the form of linking taking place, i.e. for what you wrote to be true, the GPL code would need to be linked into the same address space (e.g. binary/executable) of the other code
I haven't corrected the draft yet, Hooray
A Nasal script that calls the Canvas rendering
framework is a derivative work of the Canvas rendering framework, which is
GPL'd, so the Nasal script must be GPL'd too. However, a Nasal script as
such (i.e. one that does not call GPL licensed Nasal code) is considered
data for the Nasal interpreter and does not trigger the license.
PERMISSION & CONDITIONS
Permission is hereby granted, free of charge, to any person obtaining
a copy of the Font Software, to use, study, copy, merge, embed, modify,
redistribute, and sell modified and unmodified copies of the Font
Software, subject to the following conditions:
1) Neither the Font Software nor any of its individual components,
in Original or Modified Versions, may be sold by itself.
2) Original or Modified Versions of the Font Software may be bundled,
redistributed and/or sold with any software, provided that each copy
contains the above copyright notice and this license. These can be
included either as stand-alone text files, human-readable headers or
in the appropriate machine-readable metadata fields within text or
binary files as long as those fields can be easily viewed by the user.
...
The license is considered free by the Free Software Foundation, which states that a simple hello world program is enough to satisfy the license's requirement that fonts using the license be distributed with computer software when selling them.
Various Licenses and Comments about Them#SIL Open Font License 1.1
The Open Font License (including its original release, version 1.0) is a free copyleft license for fonts. Its only unusual requirement is that when selling the font, you must redistribute it bundled with some software, rather than alone. Since a simple Hello World program will satisfy the requirement, it is harmless. Neither we nor SIL recommend the use of this license for anything other than fonts.
Return to The FlightGear project
Users browsing this forum: No registered users and 12 guests