Re: [bug-gnu-libiconv] libiconv 1.11.1 - MS VS 2005 and manifest files

[Milan Gornik]

----- Original Message ----- 
From: "Bruno Haible" <address@hidden>
To: "Milan Gornik" <address@hidden>; <address@hidden>
Sent: Wednesday, January 16, 2008 12:04 AM
Subject: Re: [bug-gnu-libiconv] libiconv 1.11.1 - MS VS 2005 and manifest
files

> Hello Milan,
>
> ...
> Thanks for explaining. Sorry I had misunderstood the intention of your
> first
> mail.
>
> However, in this situation, and with this intent, your patch produces
> executables (iconv.exe) which cannot be distributed without violating a
> license.
>
> There is probably no problem with distributing a built libiconv.dll this
> way:
> the LGPL allows this, and you got to check your VS2005's EULA yourself.
>
> But for programs that are under the GPL, such as iconv.exe of
> libiconv 1.11.1, you are not allowed to distribute a binary that is linked
> with a closed-source library that is not part of the normal installation
> of
> the operating system. (Read the GPLv2. Read the GPLv3.) The MS
> "Redistributables" are not part of the Windows OS to which they are
> downloaded.
>
> You can certainly distribute the libiconv.dll that you built with your
> patch. But I won't apply that patch because it too easily encourages
> people
> to do things that are illegal.
>
> Bruno

Dear Bruno,

Thanks for the reply and for clarifying the situation. It was important for
me to check with you if this could be valid deployment solution for
libiconv, so thanks for sorting that out. Now I realize, though, how this
could lead to potential breach of GPL license.

Regards,
Milan Gornik