This is the mail archive of the
mailing list for the GCC project.
Re: GFDL/GPL issues
- From: Mark Mitchell <mark at codesourcery dot com>
- To: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>
- Cc: Joe dot Buck at synopsys dot com, ams at gnu dot org, bkoz at redhat dot com, dewar at adacore dot com, dnovillo at google dot com, gcc at gcc dot gnu dot org, iant at google dot com, richard dot guenther at gmail dot com, stevenb dot gcc at gmail dot com
- Date: Mon, 02 Aug 2010 19:08:45 -0700
- Subject: Re: GFDL/GPL issues
- References: <4BFC6EF0.firstname.lastname@example.org> <4C4E37FC.email@example.com> <4C4F010C.firstname.lastname@example.org> <20100727180738.GU17485@synopsys.com> <4C4F20E8.email@example.com> <AANLkTimaPhMzhw66Z6WM+n4dhe1w_ibGFpYExiCym1RC@mail.gmail.com> <AANLkTimZo8PZbrhcghxxaHPyEdW-nExj6VoL25WR3osfirstname.lastname@example.org> <4C509E54.email@example.com> <AANLkTim+nkpKL9y2kspaWejfOUd9m7xeo6qFUmNJdp8F@mail.gmail.com> <E1OeNjt-0004kn-PY@fencepost.gnu.org> <firstname.lastname@example.org> <11007291247.AA02219@vlsi1.ultra.nyu.edu> <4C5195FA.email@example.com> <4C52B176.firstname.lastname@example.org> <4C52E1C0.email@example.com> <4C53696B.firstname.lastname@example.org> <4C536B50.email@example.com> <AANLkTikQ_ajAfJu8LkCjCP_tV <AANLkTi=HYhOty0X9E6h7rDhfubFWKOjVstedUAFOCW9O@mail.gmail.com> <11008022335.AA09107@vlsi1.ultra.nyu.edu> <4C575891.firstname.lastname@example.org> <11008030058.AA09324@vlsi1.ultra.nyu.edu>
Richard Kenner wrote:
> "bad" isn't very precise. The claim was made that a reason that it's "bad"
> is that not being able to automatically generate documentation lowers
> the quality of the documentation. That's what I disagree with.
OK, fine; that's a reasonably debatable point. But, we currently can't
automatically generate manuals -- which is something we used to be able
to do -- and that's bad. In general, a policy that prevents us from
being able to use a particular technical method to achieve a goal is silly.
>> But, there is nothing that says that both kinds of documentation might
>> not be located physically in the code, so that when you
>> add/delete/modify a constraint you can also easily update the
> In that case, wouldn't we have two distinctly different kinds of material
> in the same file: an extract from a manual and code. So why couldn't
> the file have a license that says "this part is GFDL and this part is GPL"?
Maybe it could. But, maybe it can't. It depends on how closely you can
weave the documents together before you end up with something that is
more than mere aggregation.
None of this really answers the key question, which is, in my opinion,
what is the GFDL actually buying us? And, if all it's buying us is that
people can't remove the FSF's philosophical statements in manuals, is
that worth having to split hairs about exactly what parts of what
documentation can be generated in what exact manner?
(650) 331-3385 x713