Hello,
On Sat, 9 Jun 2018, at 22:19, Jan Ekström wrote:
> I think the general idea was that since LGPL lets you link an LGPL
> library in a proprietary piece of software (given that you follow the
> spirit and language of LGPL by letting people build the same version
> and making it possible for t
On Sat, Jun 09, 2018 at 22:00:40 +0200, Carl Eugen Hoyos wrote:
> > To the best of our knowledge, it is compatible with the LGPL" ?
>
> I am curious because of your follow-up in another thread:
> Why do you think it is compatible?
That's a bit of a mis-quote. That sentence is part of what is curr
On Sat, Jun 9, 2018 at 11:00 PM, Carl Eugen Hoyos wrote:
> 2018-05-29 6:53 GMT+02:00, Gyan Doshi :
>>
>> On 29-05-2018 03:34 AM, Carl Eugen Hoyos wrote:
>>
>>> Just remove "and is not known...",
>
>>> please don't state that you guarantee
>>> they are compatible.
>
> Where should we sent people wh
2018-05-29 6:53 GMT+02:00, Gyan Doshi :
>
> On 29-05-2018 03:34 AM, Carl Eugen Hoyos wrote:
>
>> Just remove "and is not known...",
>> please don't state that you guarantee
>> they are compatible.
Where should we sent people who trust what you wrote in the
documentation but had to find out it isn
On 31-05-2018 11:03 AM, Gyan Doshi wrote:
"The Fraunhofer AAC library is licensed under a license incompatible to
the GPL. Therefore, for GPL builds, you have to pass
@code{--enable-nonfree} to configure to use it. To the best of our
knowledge, it is compatible with the LGPL" ?
Will p
>> "The Fraunhofer AAC library is licensed under a license incompatible to
s/to/with/
>> the GPL. Therefore, for GPL builds, you have to pass
>> @code{--enable-nonfree} to configure to use it. To the best of our
>> knowledge, it is compatible with the LGPL" ?
- Mark
__
"The Fraunhofer AAC library is licensed under a license incompatible to
the GPL. Therefore, for GPL builds, you have to pass
@code{--enable-nonfree} to configure to use it. To the best of our
knowledge, it is compatible with the LGPL" ?
Will push in a day with above changes.
Gyan
__
On 29-05-2018 03:34 AM, Carl Eugen Hoyos wrote:
Just remove "and is not known...", please don't state that you guarantee
they are compatible.
If we are continuing to permit LGPL compilation, shouldn't it be
"The Fraunhofer AAC library is licensed under a license incompatible to
the GPL. Th
2018-05-28 12:53 GMT+02:00, Gyan Doshi :
>
>
> doc/general.texi says this for the FDK AAC library,
>
> "The Fraunhofer AAC library is licensed under a license incompatible to
> the GPL and is not known to be compatible to the LGPL. Therefore, you
> have to pass @code{--enable-nonfree} to configure
doc/general.texi says this for the FDK AAC library,
"The Fraunhofer AAC library is licensed under a license incompatible to
the GPL and is not known to be compatible to the LGPL. Therefore, you
have to pass @code{--enable-nonfree} to configure to use it."
(added 2013 in 6fe419bf73)
LICENSE
10 matches
Mail list logo
