I noticed that we don't include the Wine FAQ in the Wine documentation tarballs. So I added it but then I noticed that it was removed from the tarballs by this patch:
--- revision 1.36 date: 2003-09-18 20:51:32 +0000; author: julliard; state: Exp; lines: +9 -5 Remove the FAQ from the doc tarball, and build it as a single .html file (based on patch by Dimitrie O. Paun). ---
What's the reasoning behind this?
On Fri, Mar 18, 2005 at 01:21:06PM +0100, Francois Gouget wrote:
revision 1.36 date: 2003-09-18 20:51:32 +0000; author: julliard; state: Exp; lines: +9 -5 Remove the FAQ from the doc tarball, and build it as a single .html file (based on patch by Dimitrie O. Paun).
What's the reasoning behind this?
Well, there's not much point to create .ps and .pdf versions of it IMO. This is mostly interesting for WineHQ.
On Fri, 18 Mar 2005, Dimitrie O. Paun wrote:
On Fri, Mar 18, 2005 at 01:21:06PM +0100, Francois Gouget wrote:
revision 1.36 date: 2003-09-18 20:51:32 +0000; author: julliard; state: Exp; lines: +9 -5 Remove the FAQ from the doc tarball, and build it as a single .html file (based on patch by Dimitrie O. Paun).
What's the reasoning behind this?
Well, there's not much point to create .ps and .pdf versions of it IMO. This is mostly interesting for WineHQ.
But I don't see any reason not to put it in wine-doc-html.tar.gz or wine-doc-txt.tar.gz. The idea of these tar files is so that one can get all the Wine documentation with just one download and the FAQ is part of the documentation.
Also I don't see any evidence that the FAQ is changing faster than the rest of the documentation and is more perishable. So I see no reason to cast it apart.
On Fri, Mar 18, 2005 at 02:04:08PM +0100, Francois Gouget wrote:
But I don't see any reason not to put it in wine-doc-html.tar.gz or wine-doc-txt.tar.gz. The idea of these tar files is so that one can get all the Wine documentation with just one download and the FAQ is part of the documentation.
Yes, but I can not possibly see why would anyone want to download and read the FAQ like this. A FAQ is essentially a Web type of document, best view and browsed on the Web. By including it in those packages, we just make them bigger for 99.99% of the users that don't care about the FAQ, and those users are probably the ones that have most bandwidth restrictions anyway.
But I'm not totally against it being there, if people feel strongly that we must, I'll go with the flow.
-
Dimitrie O. Paun -
Francois Gouget