Re: GFDL and man pages
Walter Landry [EMAIL PROTECTED] writes: You can make a manpage, but you must have to include inside the manpage Actually, it's sufficient to refer to this information in the SEE ALSO section of the manpage, so that elaborateness of the GFDL doesn't interfere with the intendend use of the manpage for quick reference. Note that this all has to be _in_ the manpage. The FSF has a different view on this matter.
Re: GFDL and man pages
Florian Weimer [EMAIL PROTECTED] wrote: Walter Landry [EMAIL PROTECTED] writes: You can make a manpage, but you must have to include inside the manpage Actually, it's sufficient to refer to this information in the SEE ALSO section of the manpage, so that elaborateness of the GFDL doesn't interfere with the intendend use of the manpage for quick reference. Note that this all has to be _in_ the manpage. The FSF has a different view on this matter. The FSF doesn't read its own license. Section 4 states: In addition, you must do these things in the Modified Version: ... # H. Include an unaltered copy of this License. That looks pretty clear to me. Regards, Walter Landry [EMAIL PROTECTED]
Re: GFDL and man pages
Florian Weimer said: Walter Landry [EMAIL PROTECTED] writes: You can make a manpage, but you must have to include inside the manpage Actually, it's sufficient to refer to this information in the SEE ALSO section of the manpage, so that elaborateness of the GFDL doesn't interfere with the intendend use of the manpage for quick reference. Note that this all has to be _in_ the manpage. The FSF has a different view on this matter. Unless the FSF is the sole copyright holder of the relevant GFDL document, their interpretation of the license is irrelevant. --Joe
Re: GFDL and man pages
Walter Landry [EMAIL PROTECTED] writes: Florian Weimer [EMAIL PROTECTED] wrote: Walter Landry [EMAIL PROTECTED] writes: You can make a manpage, but you must have to include inside the manpage Actually, it's sufficient to refer to this information in the SEE ALSO section of the manpage, so that elaborateness of the GFDL doesn't interfere with the intendend use of the manpage for quick reference. Note that this all has to be _in_ the manpage. The FSF has a different view on this matter. The FSF doesn't read its own license. Section 4 states: In addition, you must do these things in the Modified Version: ... # H. Include an unaltered copy of this License. That looks pretty clear to me. It would be clear, if this were the GNU Free Manpage License. The FSF makes a claim I know I've heard here before: that there is no one-to-one mapping from files to works. They'd presumably consider all the manpages in the csound package to be a single work, and have each refer to a central gfdl(8) page. -Brian -- Brian T. Sniffen[EMAIL PROTECTED] http://www.evenmere.org/~bts/
Re: GFDL and man pages
* Brian T. Sniffen [Tue, 15 Jul 2003 at 08:34 -0400] # H. Include an unaltered copy of this License. That looks pretty clear to me. It would be clear, if this were the GNU Free Manpage License. The FSF makes a claim I know I've heard here before: that there is no one-to-one mapping from files to works. They'd presumably consider all the manpages in the csound package to be a single work, and have each refer to a central gfdl(8) page. Indeed, the manpages for gcc and friends seem to do just this. (see gcc(1), cpp(1), gfdl(7gcc), etc.) -- Hans Fugal | De gustibus non disputandum est. http://hans.fugal.net/ | Debian, vim, mutt, ruby, text, gpg http://gdmxml.fugal.net/ | WindowMaker, gaim, UTF-8, RISC, JS Bach - GnuPG Fingerprint: 6940 87C5 6610 567F 1E95 CB5E FC98 E8CD E0AA D460 pgpliE7Xqb13O.pgp Description: PGP signature
Re: GFDL and man pages
Joe Moore [EMAIL PROTECTED] writes: Unless the FSF is the sole copyright holder of the relevant GFDL document, their interpretation of the license is irrelevant. Yours is as well, and so is everyone's on this list. Then why do we discuss at all?
Re: GFDL and man pages
On Tue, 15 Jul 2003, Florian Weimer wrote: Joe Moore [EMAIL PROTECTED] writes: Unless the FSF is the sole copyright holder of the relevant GFDL document, their interpretation of the license is irrelevant. Then why do we discuss at all? The court system is the interpretation that matters. However, until we actually get a few court decisions regarding (and interpreting) the license, we're left with our reading and understanding of it. The FSF folks occasionally are more lenient with their interpretation of licenses than a very strict reading would indicate. In cases where they are the sole copyright holder, that's acceptable, especially in areas where the license is less than clear. Yet, if there is someone else holding the license, without a statement from them regarding its interpretation, we have to read the license strictly, and conservatively. [In many cases the FSF says to effect: Well, the license may or may not preclude this, but we feel that it's resonable for you to do X, Y and Z. In lieu of such a statement, we should probably assume that we cannot do X, Y, and Z, even if it would make such a license non-free.] Don Armstrong -- Clothes make the man. Naked people have little or no influence on society. -- Mark Twain http://www.donarmstrong.com http://www.anylevel.com http://rzlab.ucr.edu pgpW3Xd6sj26B.pgp Description: PGP signature
Re: GFDL and man pages
Florian Weimer [EMAIL PROTECTED] wrote: Then why do we discuss at all? Because consensus of this list is normally taken as direction for Debian action? -- MJR/slef My Opinion Only and possibly not of any group I know. Thought: Edwin A Abbott wrote about trouble with Windows in 1884
Re: GFDL and man pages
On Tue, 2003-07-15 at 12:02, Walter Landry wrote: This is a summary of what you have to do. The detailed requirements are in section 4 of the GFDL. Note that this all has to be _in_ the manpage. This may or may not make the manpage useless. You also have to include the Transparent version of the manpage, which is presumably whatever format you used to create it in. And some people wonder why I hate the GFDL. If you have treelang-3.3 installed try info treelang to see how unfriendly relevant information lookup can become. If one simply spaces through the info documentation one presses space 47 times on an 80x25 terminal before reaching Getting Started. Regards, Adam
Re: GFDL and man pages
snipped explanation of why GFDL is not good for manpages In other words, you're better off writing your own manpage from scratch. It's probably OK to look at the manual to help figure out what various options do, as long as you then put the manual away and write the manpage entirely in your own words. That's just looking up facts. Including *text* from the manual would create a derivative work. You might also want to consider asking upstream to dual-license their manual under the same terms as their program. (If they did that, people could create --help text from the manual and put it in the program, so this might help convince them to do it.) -- Nathanael Nerode neroden at gcc.gnu.org http://home.twcny.rr.com/nerode/neroden/fdl.html
