Re: [Mingw-w64-public] [Notice] gendef, genidl and genpeimg is now GPLv3 or later
Op 29 mrt. 2013 16:48 schreef JonY jo...@users.sourceforge.net het volgende: Hello, After careful thought, we have decided to make gendef, genidl and genpeimg use GPLv3 or later for all future releases. The change brings us closer to the Free software community, guaranteeing Free access to the source code for all in perpetuity, especially for the software developers and code tinkerers out there that need help. Why, if I may ask, is the public domain not good enough anymore? Ruben -- Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public -- Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [Notice] gendef, genidl and genpeimg is now GPLv3 or later
On 3/30/2013 15:47, Ruben Van Boxem wrote: Op 29 mrt. 2013 16:48 schreef JonY het volgende: Hello, After careful thought, we have decided to make gendef, genidl and genpeimg use GPLv3 or later for all future releases. The change brings us closer to the Free software community, guaranteeing Free access to the source code for all in perpetuity, especially for the software developers and code tinkerers out there that need help. Why, if I may ask, is the public domain not good enough anymore? PD unfortunately isn't encouraging constructive feedback and proper code sharing. We moved to GPLv3+ to ensure that new code additions remain Free rather than becoming partially non-Free in the near future. Note that license for previous and existing copies remain unchanged, only future trunk-based releases are affected. I don't think retrograde changes work. signature.asc Description: OpenPGP digital signature -- Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [Notice] gendef, genidl and genpeimg is now GPLv3 or later
On Sat, 30 Mar 2013 23:59:22 +0800 JonY jo...@users.sourceforge.net wrote: On 3/30/2013 15:47, Ruben Van Boxem wrote: Op 29 mrt. 2013 16:48 schreef JonY het volgende: Hello, After careful thought, we have decided to make gendef, genidl and genpeimg use GPLv3 or later for all future releases. The change brings us closer to the Free software community, guaranteeing Free access to the source code for all in perpetuity, especially for the software developers and code tinkerers out there that need help. Why, if I may ask, is the public domain not good enough anymore? PD unfortunately isn't encouraging constructive feedback and proper code sharing. We moved to GPLv3+ to ensure that new code additions remain Free rather than becoming partially non-Free in the near future. Note that license for previous and existing copies remain unchanged, only future trunk-based releases are affected. I don't think retrograde changes work. With respect to http://www.gnu.org/licenses/gpl-faq.html#WhatCaseIsOutputGPL is it true that gendef, genidl, and genpeimg do not copy any part of themselves into their output? -- Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [Notice] gendef, genidl and genpeimg is now GPLv3 or later
On 3/31/2013 04:35, Jon wrote: With respect to http://www.gnu.org/licenses/gpl-faq.html#WhatCaseIsOutputGPL is it true that gendef, genidl, and genpeimg do not copy any part of themselves into their output? That is right, the tools do not replicate themselves in anyway, nor create any call references to themselves. The tools being end products as opposed to linkable libraries provide an excellent use case for the GPLv3 license. gendef and genidl generate listings that are largely MSVC compatible, genpeimg modifies PE flags. signature.asc Description: OpenPGP digital signature -- Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [Notice] gendef, genidl and genpeimg is now GPLv3 or later
On Sat, Mar 30, 2013 at 9:28 PM, JonY jo...@users.sourceforge.net wrote: On 3/31/2013 04:35, Jon wrote: With respect to http://www.gnu.org/licenses/gpl-faq.html#WhatCaseIsOutputGPL is it true that gendef, genidl, and genpeimg do not copy any part of themselves into their output? That is right, the tools do not replicate themselves in anyway, nor create any call references to themselves. The tools being end products as opposed to linkable libraries provide an excellent use case for the GPLv3 license. gendef and genidl generate listings that are largely MSVC compatible, genpeimg modifies PE flags. Doesn't gendef place restriction on the files it generates? -- Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [Notice] gendef, genidl and genpeimg is now GPLv3 or later
On Sat, 30 Mar 2013 22:51:34 -0400 NightStrike nightstr...@gmail.com wrote: On Sat, Mar 30, 2013 at 9:28 PM, JonY jo...@users.sourceforge.net wrote: On 3/31/2013 04:35, Jon wrote: With respect to http://www.gnu.org/licenses/gpl-faq.html#WhatCaseIsOutputGPL is it true that gendef, genidl, and genpeimg do not copy any part of themselves into their output? That is right, the tools do not replicate themselves in anyway, nor create any call references to themselves. The tools being end products as opposed to linkable libraries provide an excellent use case for the GPLv3 license. gendef and genidl generate listings that are largely MSVC compatible, genpeimg modifies PE flags. Doesn't gendef place restriction on the files it generates? If I understand the GPL faq entry correctly, the output of a GPL program that does not copy part of itself to its output is not covered by the GPL, so use of that output is unencumbered by the GPL. It appears your question could only be true if gendef's output is covered by something in addition to GPLv3. As JonY stated GPLv3 or later and not GPLv3 + XYZ, I'm going to assume until I hear otherwise that gendef is restricted only by the GPLv3 terms, JonY's technical response remains valid, and that the above GPL faq entry is the correct guidance to follow when consuming gendef's output. But I'm not a lawyer, and now just a bit more curious. -- Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2 ___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [Notice] gendef, genidl and genpeimg is now GPLv3 or later
On 3/31/2013 10:51, NightStrike wrote: On Sat, Mar 30, 2013 at 9:28 PM, JonY jo...@users.sourceforge.net wrote: On 3/31/2013 04:35, Jon wrote: With respect to http://www.gnu.org/licenses/gpl-faq.html#WhatCaseIsOutputGPL is it true that gendef, genidl, and genpeimg do not copy any part of themselves into their output? That is right, the tools do not replicate themselves in anyway, nor create any call references to themselves. The tools being end products as opposed to linkable libraries provide an excellent use case for the GPLv3 license. gendef and genidl generate listings that are largely MSVC compatible, genpeimg modifies PE flags. Doesn't gendef place restriction on the files it generates? No, there are no known restrictions, besides: http://www.gnu.org/licenses/gpl-faq.html#GPLOutput From the text: 8= Is there some way that I can GPL the output people get from use of my program? For example, if my program is used to develop hardware designs, can I require that these designs must be free? In general this is legally impossible; copyright law does not give you any say in the use of the output people make from their data using your program. If the user uses your program to enter or convert his own data, the copyright on the output belongs to him, not you. More generally, when a program translates its input into some other form, the copyright status of the output inherits that of the input it was generated from. So the only way you have a say in the use of the output is if substantial parts of the output are copied (more or less) from text in your program. For instance, part of the output of Bison (see above) would be covered by the GNU GPL, if we had not made an exception in this specific case. You could artificially make a program copy certain text into its output even if there is no technical reason to do so. But if that copied text serves no practical purpose, the user could simply delete that text from the output and use only the rest. Then he would not have to obey the conditions on redistribution of the copied text. 8= The gendef program does none of those. signature.asc Description: OpenPGP digital signature -- Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
Re: [Mingw-w64-public] [Notice] gendef, genidl and genpeimg is now GPLv3 or later
On 3/31/2013 12:32, Jon wrote: On Sat, 30 Mar 2013 22:51:34 -0400 NightStrike nightstr...@gmail.com wrote: On Sat, Mar 30, 2013 at 9:28 PM, JonY jo...@users.sourceforge.net wrote: On 3/31/2013 04:35, Jon wrote: With respect to http://www.gnu.org/licenses/gpl-faq.html#WhatCaseIsOutputGPL is it true that gendef, genidl, and genpeimg do not copy any part of themselves into their output? That is right, the tools do not replicate themselves in anyway, nor create any call references to themselves. The tools being end products as opposed to linkable libraries provide an excellent use case for the GPLv3 license. gendef and genidl generate listings that are largely MSVC compatible, genpeimg modifies PE flags. Doesn't gendef place restriction on the files it generates? If I understand the GPL faq entry correctly, the output of a GPL program that does not copy part of itself to its output is not covered by the GPL, so use of that output is unencumbered by the GPL. It appears your question could only be true if gendef's output is covered by something in addition to GPLv3. As JonY stated GPLv3 or later and not GPLv3 + XYZ, I'm going to assume until I hear otherwise that gendef is restricted only by the GPLv3 terms, JonY's technical response remains valid, and that the above GPL faq entry is the correct guidance to follow when consuming gendef's output. GPLv3 does not allow additional restrictions and conditions to be added, doing so would make the program non-redistributable as it cannot legally comply with GPLv3 if copied. signature.asc Description: OpenPGP digital signature -- Own the Future-Intel(R) Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2___ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
