NOTE: Please publicize any license changes to your packages

[Tomas Mraz]

On Tue, 2007-07-24 at 22:18 +0200, Ralf Ertzinger wrote:
> Hi.
> 
> On Tue, 24 Jul 2007 22:10:18 +0200, Tomas Mraz wrote
> 
> > And I don't even see the problem with lgplv3 - we just have to ensure
> > that we don't link any gplv2 only program to such library. Such as we
> > have to ensure that we don't link any gpl program to openssl library
> > and so on.
> 
> Errr.. like these?
> 
> stunnel: GPL
> ssmtp: GPL
> wget: GPL
> slrn: GPL
> htdig: GPL
> cadaver: GPL
> pam_ccreds: GPL
> lftp: GPL
> openvpn: GPL
> ctorrent: GPL
> elinks: GPL
> wpa_supplicant: GPL
> perl-Crypt-SSLeay: GPL or Artistic
> libdhcp6client: GPL
> xen: GPL
> dhcpv6_client: GPL
> git-core: GPL
> fetchmail: GPL
> rdesktop: GPL
> claws-mail: GPL
> claws-mail-plugins-pgp: GPL
> gkrellm: GPL

Either they have exception for linking with openssl or we are already
breaking the licenses and we should stop doing that. Why nobody noticed
that earlier?
-- 
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
                                              Turkish proverb