docs/en wine-faq.sgml

Dimi Paun dimi at
Tue May 17 14:54:29 CDT 2005

ChangeSet ID:	11163596690526244696966423
CVSROOT:	/cvsroot/wine
Module name:	docs
Changes by:	dimi at	2005/05/17 12:54:29

Modified files:
	en             : wine-faq.sgml 

Log message:
	Brian Vincent <vinn at>
	Add FAQ about updating the FAQ and submitting patches.
	Add FAQ about the various Wine branches.
	Fix broken SGML.

Old revision  New revision  Changes     Path
 1.3           1.4           +96 -9      docs/en/wine-faq.sgml

Index: docs/en/wine-faq.sgml
diff -u -p docs/en/wine-faq.sgml:1.3 docs/en/wine-faq.sgml:1.4
--- docs/en/wine-faq.sgml	17 May 2005 19:54:29 -0000
+++ /dev/null	17 May 2005 19:54:29 -0000
@@ -26,6 +26,35 @@
         <para>It may be reproduced and modified under the same terms as Wine itself.</para>
+      <question id="How-can-I-update-the-FAQ">
+        <para>How can I update this FAQ?</para>
+      </question>
+      <answer>
+        <para>This FAQ lives in the CVS repository on SourceForge.  In order
+ to update this document you'll need to checkout the the docs from
+ CVS, edit it, and then send a patch.  In order to get the docs, run
+ the following CVS command:</para>
+ <screen>
+cvs -z3 -d:pserver:anonymous at co -P docs
+ </screen>
+ <para>
+ When prompted for a password, just press the enter key.  </para>
+ <para> 
+ A subdirectory
+ named docs will be created.  If you navigate through there you'll
+ find the FAQ in <filename>docs/en/wine-faq.sgml</filename>.  
+ The file is written in SGML, which is simply a superset of HTML.
+ You can use your favorite text editor to make changes to it but
+ be sure to make sure each opening tag has a corresponding closing
+ tag.  You may find the <command>tidy</command> or 
+ <command>xmllint</command> utilities useful for editing the document.
+ </para>
+        <para>After editing the file, 
+ <ulink url="">
+          generate a patch</ulink> against CVS and
+ email it to wine-patches at</para>
+      </answer>
+      </qandaentry>
     <qandadiv id="General-Questions-about-Wine">
       <title>General Questions about Wine</title>
@@ -170,11 +199,11 @@
           Two projects have started along those lines: <ulink
-          url="">QEMU</>, an
+          url="">QEMU</ulink>, an
           open-source project, and <ulink
-          url="">Dynamite</>,
+          url="">Dynamite</ulink>,
           a commercial CPU emulator environment from
-          <ulink url="">Transitives Technologies</>.
+          <ulink url="">Transitives Technologies</ulink>.
@@ -266,13 +295,71 @@
           However, if you want to reuse Windows drivers on a non-Microsoft
           operating system we recommend that you have a look at
-          <ulink url="">ReactOS</>.
+          <ulink url="">ReactOS</ulink>.
+      <question id="What-software-is-based-on-Wine">
+        <para>What software projects are based on Wine and how are they
+ related?</para>
+      </question>
+      <answer>
+        <para>If you trace Wine's roots back, you'll find quite a few 
+ different projects have emerged.  For complete details, look at
+ the <ulink url="">Wine history</ulink>
+ page to learn how these diverged.
+        </para>
+ <para>
+ In the beginning, the only version of Wine that existed was managed
+ by Alexandre.  This eventually became to be known as the WineHQ
+ tree.  From there, all other branches diverged.  One of the first
+ ones to be developed outside of WineHQ was done by Corel in 1998 in 
+ support of their Wine efforts.  Even though Wine was developed under 
+ the X11 (BSD-like) license, Corel resubmitted most of their changes 
+ back to WineHQ.  Corel eventually moved on as well as their development
+ team.  Many changes from Corel made their way back into the WineHQ
+ tree.
+ </para>
+ <para>
+ In 2002 the main WineHQ tree changed licenses to LGPL and caused
+ Wine to fork.  The original X11 code is available on SourceForge as 
+ the <ulink url="">ReWind</ulink> project.
+ For all intents and purposes, this is a dead project.  The code
+ has diverged drastically from WineHQ's and any updates that do
+ appear are infrequent.  Anyone wishing to utilize the old Wine code
+ under the old X11 license should strongly consider otherwise.
+ </para>
+ <para>
+ As Corel was ending their efforts, two new companies emerged with
+ their own versions of Wine.  CodeWeavers' developed their CrossOver
+ line of products and TransGaming developed WineX (now called Cedega.)
+ CodeWeavers continues to develop their products based on Wine and
+ actively supports the community.  Their development model consists
+ of contributing directly to the WineHQ tree and branching periodically
+ for releases.  TransGaming's WineX/Cedega product followed the
+ X11 split.  Much of their code has been relicensed under 
+ the Aladdin Free Public License limiting the distribution.
+ TransGaming has since adopted some of the libraries from the WineHQ 
+ tree and they remain under the LGPL license.  TransGaming maintains
+ informal contact with the Wine community but has not contributed 
+ anything to Wine in a number of years.
+ </para>
+ <para>
+ If your primary concern is to use a free version of Wine (as in beer 
+ as well as right-to-use), then you're probably most interested in 
+ utilizing the WineHQ tree.  If you want a commercial product (including 
+ all the features like support) developed by a company that actively 
+ contributes to Wine, then you should check out the CodeWeavers' 
+ products described below.  If you simply want to run games, 
+ TransGaming's Cedega might be a solution.
+ </para>
+      </answer>
+      </qandaentry>
+      <qandaentry>
       <question id="Which-one-of-the-different-Wine-packages">
         <para>Which one of the different Wine packages out there is good for me?</para>
@@ -561,7 +648,7 @@
           Mac OS X / Darwin: The <ulink
-          url="">Darwine</> is
+          url="">Darwine</ulink> is
           currently working on porting Wine to the Darwin/x86 platform. Their
           goal is to eventually make it possible to run x86 Windows
           applications on Darwin/PPC and then Mac OS X by using Bochs.
@@ -869,7 +956,7 @@
           It should also be available from any other site that mirrors 
-, see <ulink url=""></>.
+, see <ulink url=""></ulink>.
           Some of these sites may archive previous versions of Wine as well as the
           current one. To determine which is the latest one, look at the 
           distribution file name, which will take the form 
@@ -1614,11 +1701,11 @@ export PATH=$PATH:/path/to/wine/binary 
           Submitting a patch for inclusion in Wine is pretty simple.
           Basically all you have to do is send the patch to the
           wine-patches mailing list 
-          (<ulink url=""></>).
+          (<ulink url=""></ulink>).
           Still there are a couple of recommendations about the patch format
           and all so it's best to read our page describing <ulink
           url="">how to submit
-          patches</>. This will also give you more details about the whole
+          patches</ulink>. This will also give you more details about the whole
           process and in particular to what will happen to your patch once
@@ -1688,7 +1775,7 @@ export PATH=$PATH:/path/to/wine/binary 
             MusicMatch Jukebox 5 has also been
-            <ulink url="">ported</>
+            <ulink url="">ported</ulink>
             to Linux using Winelib. However more recent versions have not, and
             version 5 is no longer available.

More information about the wine-cvs mailing list