On Mon, Jun 27, 2005 at 06:53:59AM -0700, magnus@itkonsult-olsen.com wrote:
http://www.gnu.org/licenses/gpl.html <- url to gpl licen
http://www.gnu.org/licenses/lgpl.html ^ URL to LGPL license ^
read paragrpah 2 c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)
Read LGPL section 3 3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices.
Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of the Library into a program that is not a library.
the text above are from gpl and I have include where to obtain the gpl licen.
The text above is from the LGPL, and I have included where to obtain the LGPL license.
If I do not complete wrong we are relasng wine dll
as
lgpl in the source there not gpl.
DING! Therefore, the GPL does NOT apply, the *LGPL* terms I quoted above DO apply.
therefor it become a sublicen, we do not change the licen from lgpl to gpl. if you reading wine source code for wine dll files you will see it is under lgpl not gpl.
DING! Also correct. But as soon as I get the LGPL files, I can invoke clause 3, and BAM! They are now GPL'd. No sublicensing is involved. The LGPL has the same practical effect as dual-licensing the code as LGPL/GPL.
Note that I pointed this out way back in the conversation:
I don't really understand what you're trying to say here. However, note that the LGPL allows you to "upgrade" to the GPL license (it's effectively a dual license). The LGPL states:
- You may opt to apply the terms of the
ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices.
Thus, there is no sublicensing going on -- it's all one license (GPL).
<282 lines snipped>
So, again -- DUAL licensing, NOT sublicensing.
-- Travis
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
I know you can make lgpl to gpl that is not the problem. reactos main licen is gpl. right. And gpl say you are not allown to change a sublicen to another licen. right.
than mean all other modules that are using a diffent licen like lgpl as wine dll does. it will become a sublicen. And 3d part like hotlix can not change any sublicen that reactos is using. they must release with same licen.
But if we in ros have change lgpl to gpl that is allown. or if hotlix did take the source direcly from wine. often are we using modify wine dll files and some part of the code will never goes back to wine, for it is reactos specfiy so it will working in reactos or windows, that will not work in wine under linux. Some other dll are under bsd licen, I have not check see if they have change that licen. but problade they have.
Quoting Quandary ai2097@yahoo.com:
On Mon, Jun 27, 2005 at 06:53:59AM -0700, magnus@itkonsult-olsen.com wrote:
http://www.gnu.org/licenses/gpl.html <- url to gpl licen
http://www.gnu.org/licenses/lgpl.html ^ URL to LGPL license ^
read paragrpah 2 c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)
Read LGPL section 3 3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices.
Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of the Library into a program that is not a library.
the text above are from gpl and I have include where to obtain the gpl licen.
The text above is from the LGPL, and I have included where to obtain the LGPL license.
If I do not complete wrong we are relasng wine dll
as
lgpl in the source there not gpl.
DING! Therefore, the GPL does NOT apply, the *LGPL* terms I quoted above DO apply.
therefor it become a sublicen, we do not change the licen from lgpl to gpl. if you reading wine source code for wine dll files you will see it is under lgpl not gpl.
DING! Also correct. But as soon as I get the LGPL files, I can invoke clause 3, and BAM! They are now GPL'd. No sublicensing is involved. The LGPL has the same practical effect as dual-licensing the code as LGPL/GPL.
Note that I pointed this out way back in the conversation:
I don't really understand what you're trying to say here. However, note that the LGPL allows you to "upgrade" to the GPL license (it's effectively a dual license). The LGPL states:
- You may opt to apply the terms of the
ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices.
Thus, there is no sublicensing going on -- it's all one license (GPL).
<282 lines snipped>
So, again -- DUAL licensing, NOT sublicensing.
-- Travis
Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Ros-dev mailing list Ros-dev@reactos.com http://reactos.com:8080/mailman/listinfo/ros-dev
-
magnus＠itkonsult-olsen.com -
Quandary