libgcrypt in Sage is GPL 3

[sagetrac-drkirkby]

Sage has libgcrypt version 1.4.3 in spkg/standard.

But:

http://directory.fsf.org/project/libgcrypt/

clearly shows:

1.4.3

• Released: 21 Nov, 2008
• Code Maturity: Stable
• Source Archive: http://www.gnupg.org/download/index.en.html#lib...
• Licenses: GPLv3
• Interfaces: Command Line

The file SPKG.txt says:

License

• LGPL V2.1 or later (1.4 release)

Component: cryptography

Issue created by migration from https://trac.sagemath.org/ticket/6757

[wdjoyner]

comment:1

See also #1627
When I download libcrypt-1.4.4 from http://www.gnupg.org/download/index.en.html#libgcrypt
the COPYING file indicates GPLv2 and the COPYING.LIB file indicates LGPLv2.1.

I don't see 1.4.3 there.

[sagetrac-drkirkby]

comment:2

The name of the .spkg file in Sage 4.1.1 is libgcrypt-1.4.3.p1.spkg I've made a libgcrypt-1.4.3.p2.spkg

drkirkby@smudge:[~/sage/suncc/sage-4.1.1/spkg/standard] $ ls -ld libgcrypt* 
-rw-r--r--   1 drkirkby other    2036701 Jul 31 22:45 libgcrypt-1.4.3.p1.spkg
-rw-r--r--   1 drkirkby other    2115840 Aug 16 12:34 libgcrypt-1.4.3.p2.spkg
drkirkby@smudge:[~/sage/suncc/sage-4.1.1/spkg/standard] $ pwd
/export/home/drkirkby/sage/suncc/sage-4.1.1/spkg/standard
drkirkby@smudge:[~/sage/suncc/sage-4.1.1/spkg/standard] $

[sagetrac-drkirkby]

comment:3

I guess we should go by the COPYING file. The website and the actual code disagree. I assume the code is more authorative.

I suspect this should be closed in that case.

[sagetrac-mvngu]

comment:4

I think the file COPYING in the source tarball is the authority here. So close this ticket as invalid.