From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-32676-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 28099 invoked by alias); 1 Aug 2008 18:35:57 -0000
Received: (qmail 28086 invoked by uid 22791); 1 Aug 2008 18:35:56 -0000
X-Spam-Check-By: sourceware.org
Received: from mtaout4.012.net.il (HELO mtaout4.012.net.il) (84.95.2.10)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 01 Aug 2008 18:35:33 +0000
Received: from HOME-C4E4A596F7 ([84.229.228.238]) by i_mtaout4.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0K4X0052GQBFO170@i_mtaout4.012.net.il> for gdb@sourceware.org; Fri, 01 Aug 2008 21:35:40 +0300 (IDT)
Date: Fri, 01 Aug 2008 18:35:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Autogenerate gdbarch doc for internals manual
In-reply-to: <Pine.LNX.4.64.0808011719410.3945@digraph.polyomino.org.uk>
X-012-Sender: halo1@inter.net.il
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: stan@codesourcery.com, gdb@sourceware.org
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <uhca4mvm3.fsf@gnu.org>
References: <4893427D.1000909@codesourcery.com> <Pine.LNX.4.64.0808011719410.3945@digraph.polyomino.org.uk>
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2008-08/txt/msg00029.txt.bz2

> Date: Fri, 1 Aug 2008 17:22:12 +0000 (UTC)
> From: "Joseph S. Myers" <joseph@codesourcery.com>
> cc: gdb@sourceware.org
> 
> You have the issue that's been discussed before in the GCC context: the 
> need for an appropriate license text on gdbarch.sh to allow parts of it to 
> be used in the manual that's under a different license from the code.  

That depends on how Stan writes those parts.  We could, for instance,
have some template outside gdbarch.sh which the script will edit to
produce the actual Texinfo.

In general, there's any number of ways to do this job without
violating the GNU licenses.

> Good luck getting the FSF to produce a GPLv3 exception text for this in 
> reasonable time given how long all the other exceptions have taken so far 

RMS always asserted that such jobs will not present any
license-related problems in practice.  I can run the idea through him
in advance and see if he has any specific advice, if Stan would like
that before he embarks on doing this job.