[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Savannah-register-public] [task #9954] Submission of HOTP Toolkit
From: |
Simon Josefsson |
Subject: |
[Savannah-register-public] [task #9954] Submission of HOTP Toolkit |
Date: |
Tue, 08 Dec 2009 21:33:07 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091112 Iceweasel/3.5.5 (like Firefox/3.5.5; Debian-3.5.5-1) |
Follow-up Comment #2, task #9954 (project administration):
Hi!
Do you refer to the auto-generated gtk-doc stuff? I have added a paragraph
in it now explaining that it is all auto-generated from the source code (which
is LGPLv2.1+) and also added a pointer to the COPYING file.
link-warning.h is copied from gnulib (already hosted on savannah), I've asked
them to add a license header to it, and temporarily added a LGPLv2.1+ header
to it in the hotp-toolkit package.
I believe the Makefile.in copyright/license is typical and intentional: it
combines one part (Makefile.am from me) with another part (from automake) to
generate Makefile.in. Each part has its own licensing information. I don't
see any way to de-confuse that situation without losing important legal
information?
Thanks,
/Simon
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/task/?9954>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/