On 4 August 2010 21:03, Alfred M. Szmidt <a...@gnu.org> wrote: > > I have read the thread in full, and I do not see the problem with > > keeping that info in a seperate manual; GCC has so many options > > for various architectures and systems that I think it makes > > technical sense to have a "Invoking GCC" manual. > > And what about libstdc++ API docs, which are currently quite > difficult to cross-reference with the libstdc++ manual, and cannot > be included in it? The API docs come from C++ sources and the > manual from docbook sources, so texinfo has nothing to do with it. > > For a API reference listing document, it would make more sense to > license the work under the GPL, is that possible?
Possible? It's required, because it's generated from C++ sources covered by the GPL. What makes you think making the API reference GPL would help? The manual is GFDL. So they can't be combined. That's a problem. The documentation I write for the libstdc++ manual and the documentation I write for libstdc++ API reference cannot be combined, or merged, or derived from each other. Take it from someone who actually does write the stuff: it's annoying.
