Re: [Development] State of LGPL exception after migration to LGPLv3

2018-05-31 Thread Lars Knoll
> On 1 Jun 2018, at 08:28, Edward Welbourne wrote: > > Em segunda-feira, 17 de abril de 2017, às 04:24:25 PDT, Konstantin Tokarev > escreveu: 1. Is it still legal to incorporate "inline functions and templates" into code not covered by LGPLv3? In particular, I'm interested in qAsC

Re: [Development] State of LGPL exception after migration to LGPLv3

2018-05-31 Thread Edward Welbourne
Em segunda-feira, 17 de abril de 2017, às 04:24:25 PDT, Konstantin Tokarev escreveu: >>> 1. Is it still legal to incorporate "inline functions and templates" >>> into code not covered by LGPLv3? In particular, I'm interested in >>> qAsConst On 17 Apr 2017, at 18:07, Thiago Macieira wrote: >> The

Re: [Development] State of LGPL exception after migration to LGPLv3

2017-04-18 Thread Lars Knoll
The LGPL_EXCEPTION.txt files should get removed from our sources. LGPLv3 covers this case directly. Cheers, Lars > On 17 Apr 2017, at 18:07, Thiago Macieira wrote: > > Em segunda-feira, 17 de abril de 2017, às 04:24:25 PDT, Konstantin Tokarev > escreveu: >> 1. Is it still legal to incorporat

Re: [Development] State of LGPL exception after migration to LGPLv3

2017-04-17 Thread Thiago Macieira
Em segunda-feira, 17 de abril de 2017, às 04:24:25 PDT, Konstantin Tokarev escreveu: > 1. Is it still legal to incorporate "inline functions and templates" into > code not covered by LGPLv3? In particular, I'm interested in qAsConst The LGPLv3 text contains the equivalent exception. See LICENSE.L

[Development] State of LGPL exception after migration to LGPLv3

2017-04-17 Thread Konstantin Tokarev
Hello, There is LGPL_EXCEPTION.txt that says: - As an additional permission to the GNU Lesser General Public License version 2.1, the object code form of a "work that uses the Library" may incorporate material from a header file that is part of the Library. You may distribute such ob