This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
License of code in info documentation
- From: Reuben Thomas <rrt at sc3d dot org>
- To: glibc-bugs at sourceware dot org
- Subject: License of code in info documentation
- Domainkey-signature: a=rsa-sha1; s=key1024; d=sc3d.org; c=nofws; q=dns; b=Evu3Q/970KPhy17DdYLhr/zmVBV7J4jFv5mphcC8w03fDvmbUJcp8b0JOccUJqUpeCDZ8G6MiQxDcOp/mzQvImI2SGiV4xWQgGkSOHefjOJ2oKGhOkJ+rHYMBhh0kdO8doKBHLYCP9MdDvy49YPmoUr1FOXPQ3N3wYd2a/DZSDs=
I want to use code from the info documentation of glibc in a GPLed
project. I can't find any statement on the license of the code examples
other than that the manual is under the GFDL. I couldn't find any
information on this by searching the internet or the mailing list
archive (in fact, the mailing list archive search seems broken, as I
can't make it return matches for any search, even words occurring in
past postings to the list).
So:
1. What is the license of the code in the info documentation?
2. If it's not licensed separately from the documentation, then can I
use it anyway? (In my case, this question is the same as "Is the GFDL
compatible with the GPL?"). I appreciate this might not be the right
place to ask that question.
3. If the code in the info docs is not licensed separately from the
documentation, would the developers consider licensing it under the same
license as glibc itself?
--
http://rrt.sc3d.org/ | sad, a. the efforts of musical debutantes (Bierce)