forked from Mirrors/wine-wine
Tweak the screen sections.
Add various tags such as: prompt, userinput, replaceable, filename. Use '</>' to close tags.oldstable
parent
8e84fedab6
commit
4c3ab4812e
|
@ -62,7 +62,7 @@
|
||||||
single command, as root:
|
single command, as root:
|
||||||
</para>
|
</para>
|
||||||
<screen>
|
<screen>
|
||||||
# apt-get install wine
|
<prompt># </><userinput>apt-get install wine</>
|
||||||
</screen>
|
</screen>
|
||||||
<para>
|
<para>
|
||||||
<command>apt-get</command> will connect to a Debian archive
|
<command>apt-get</command> will connect to a Debian archive
|
||||||
|
@ -95,10 +95,10 @@
|
||||||
might perform the following actions to install it:
|
might perform the following actions to install it:
|
||||||
</para>
|
</para>
|
||||||
<screen>
|
<screen>
|
||||||
$ su -
|
<prompt>$ </><userinput>su -</>
|
||||||
<emphasis><Type in root password></emphasis>
|
Password:
|
||||||
# cd /home/user
|
<prompt># </><userinput>cd /home/user</>
|
||||||
# dpkg -i wine_0.0.20021031-1.deb
|
<prompt># </><userinput>dpkg -i wine_<replaceable>0.0.20021031-1</>.deb</>
|
||||||
</screen>
|
</screen>
|
||||||
<para>
|
<para>
|
||||||
You may also want to install the
|
You may also want to install the
|
||||||
|
@ -131,7 +131,7 @@ $ su -
|
||||||
Once there, type this one command as root:
|
Once there, type this one command as root:
|
||||||
</para>
|
</para>
|
||||||
<screen>
|
<screen>
|
||||||
# rpm -ivh wine-20020605-2.i386.rpm
|
<prompt># </><userinput>rpm -ivh wine-<replaceable>20020605-2.i386</>.rpm</>
|
||||||
</screen>
|
</screen>
|
||||||
<para>
|
<para>
|
||||||
You may also want to install the
|
You may also want to install the
|
||||||
|
@ -218,23 +218,24 @@ $ su -
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
<para>
|
<para>
|
||||||
The official releases are tagged by date with the format
|
The official releases are tagged by date with the format
|
||||||
"Wine-YYYYMMDD.tar.gz". Your best bet is to grab the latest
|
"Wine-<replaceable>YYYYMMDD</>.tar.gz". Your best bet is to grab
|
||||||
one.
|
the latest one.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
Once you have downloaded this, you must first compile wine, and then install it.
|
Once you have downloaded this, you must first compile wine, and then
|
||||||
To do this is not very hard. First switch to the directory containing the file
|
install it. This is not very hard to do. First switch to the
|
||||||
you just downloaded. Then extract the source with (e.g.):
|
directory containing the file you just downloaded. Then extract the
|
||||||
</para>
|
source with (e.g.):
|
||||||
<screen>
|
<screen>
|
||||||
# tar xzvf wine-20021031.tar.gz
|
<prompt># </><userinput>tar xzvf wine-<replaceable>20021031</>.tar.gz</>
|
||||||
</screen>
|
</screen>
|
||||||
|
</para>
|
||||||
<para>
|
<para>
|
||||||
Then, switch to the directory that was created and compile it by typing (e.g.):
|
Then, switch to the directory that was created and compile it by typing (e.g.):
|
||||||
</para>
|
|
||||||
<screen>
|
<screen>
|
||||||
# ./tools/wineinstall
|
<prompt># </><userinput>./tools/wineinstall</>
|
||||||
</screen>
|
</screen>
|
||||||
|
</para>
|
||||||
<para>
|
<para>
|
||||||
NOTE: You must make sure that you are not the superuser (root) when doing this,
|
NOTE: You must make sure that you are not the superuser (root) when doing this,
|
||||||
and that you have write permission to the directory that was created by the tar
|
and that you have write permission to the directory that was created by the tar
|
||||||
|
@ -248,21 +249,21 @@ $ su -
|
||||||
<para>
|
<para>
|
||||||
The official web page for Wine CVS is
|
The official web page for Wine CVS is
|
||||||
<ulink url="http://www.winehq.com/development/">
|
<ulink url="http://www.winehq.com/development/">
|
||||||
http://www.winehq.com/development/</ulink>.
|
http://www.winehq.com/development/</>.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
First, you need to get a copy of the latest Wine sources
|
First, you need to get a copy of the latest Wine sources
|
||||||
using CVS. You can tell it where to find the source tree by
|
using CVS. You can tell it where to find the source tree by
|
||||||
setting the <envar>CVSROOT</envar> environment variable. You
|
setting the <envar>CVSROOT</envar> environment variable. You
|
||||||
also have to log in anonymously to the wine CVS server. In
|
also have to log in anonymously to the wine CVS server. In
|
||||||
<command>bash</command>, it might look something like this:
|
<command>bash</>, it might look something like this:
|
||||||
</para>
|
|
||||||
<screen>
|
<screen>
|
||||||
$ export CVSROOT=:pserver:cvs@cvs.winehq.com:/home/wine
|
<prompt>$ </><userinput>export CVSROOT=:pserver:cvs@cvs.winehq.com:/home/wine</>
|
||||||
$ cvs login
|
<prompt>$ </><userinput>cvs login</>
|
||||||
Password: cvs
|
Password:
|
||||||
$ cvs checkout wine
|
<prompt>$ </><userinput>cvs checkout wine</>
|
||||||
</screen>
|
</screen>
|
||||||
|
</para>
|
||||||
<para>
|
<para>
|
||||||
That'll pull down the entire Wine source tree from
|
That'll pull down the entire Wine source tree from
|
||||||
winehq.com and place it in the current directory (actually
|
winehq.com and place it in the current directory (actually
|
||||||
|
@ -270,37 +271,37 @@ $ cvs checkout wine
|
||||||
parameters, so there are many ways to pull down files, from
|
parameters, so there are many ways to pull down files, from
|
||||||
anywhere in the revision history. Later, you can grab just
|
anywhere in the revision history. Later, you can grab just
|
||||||
the updates:
|
the updates:
|
||||||
</para>
|
|
||||||
<screen>
|
<screen>
|
||||||
$ cvs -PAd update
|
<prompt>$ </><userinput>cvs -PAd update</>
|
||||||
</screen>
|
</screen>
|
||||||
|
</para>
|
||||||
<para>
|
<para>
|
||||||
<command>cvs update</command> works from inside the source tree.
|
<command>cvs update</> works from inside the source tree.
|
||||||
You don't need the <envar>CVSROOT</envar> environment variable
|
You don't need the <envar>CVSROOT</> environment variable
|
||||||
to run it either. You just have to be inside the source tree.
|
to run it either. You just have to be inside the source tree.
|
||||||
The <parameter>-P</parameter>, <parameter>-A</parameter> and <parameter>-d</parameter>
|
The <parameter>-P</>, <parameter>-A</> and <parameter>-d</>
|
||||||
options make sure your local Wine tree directory structure stays
|
options make sure your local Wine tree directory structure stays
|
||||||
in sync with the remote repository.
|
in sync with the remote repository.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
After you've made changes, you can create a patch with
|
After you've made changes, you can create a patch with
|
||||||
<command>cvs diff -u</command>, which sends output to stdout
|
<command>cvs diff -u</>, which sends output to stdout
|
||||||
(the <parameter>-u</parameter> controls the format of the
|
(the <parameter>-u</> controls the format of the
|
||||||
patch). So, to create an <filename>my_patch.diff</filename>
|
patch). So, to create an <filename>my_patch.diff</>
|
||||||
file, you would do this:
|
file, you would do this:
|
||||||
</para>
|
|
||||||
<screen>
|
<screen>
|
||||||
$ cvs diff -u > my_patch.diff
|
<prompt>$ </><userinput>cvs diff -u ><replaceable>my_patch.diff</></>
|
||||||
</screen>
|
</screen>
|
||||||
|
</para>
|
||||||
<para>
|
<para>
|
||||||
You can call <command>cvs diff</command> from anywhere in the
|
You can call <command>cvs diff</command> from anywhere in the
|
||||||
tree (just like <command>cvs update</command>), and it will
|
tree (just like <command>cvs update</command>), and it will
|
||||||
always grab recursively from that point. You can also specify
|
always grab recursively from that point. You can also specify
|
||||||
single files or subdirectories:
|
single files or subdirectories:
|
||||||
</para>
|
|
||||||
<screen>
|
<screen>
|
||||||
$ cvs diff -u dlls/winaspi > my_aspi_patch.diff
|
<prompt>$ </><userinput>cvs diff -u dlls/winaspi ><replaceable>my_aspi_patch.diff</></>
|
||||||
</screen>
|
</screen>
|
||||||
|
</para>
|
||||||
<para>
|
<para>
|
||||||
Experiment around a little. It's fairly intuitive.
|
Experiment around a little. It's fairly intuitive.
|
||||||
</para>
|
</para>
|
||||||
|
@ -313,55 +314,54 @@ $ cvs diff -u dlls/winaspi > my_aspi_patch.diff
|
||||||
distribution, you have the option of applying patches to the
|
distribution, you have the option of applying patches to the
|
||||||
source tree to fix bugs and add experimental features.
|
source tree to fix bugs and add experimental features.
|
||||||
Perhaps you've found a bug, reported it to the <ulink
|
Perhaps you've found a bug, reported it to the <ulink
|
||||||
url="mailto:wine-devel@winehq.com">Wine mailing list</ulink>,
|
url="mailto:wine-devel@winehq.com">Wine mailing list</>,
|
||||||
and received a patch file to fix the bug. You can apply the
|
and received a patch file to fix the bug. You can apply the
|
||||||
patch with the <command>patch</command> command, which takes a
|
patch with the <command>patch</> command, which takes a
|
||||||
streamed patch from <filename>stdin</filename>:
|
streamed patch from <filename>stdin</>:
|
||||||
</para>
|
|
||||||
<screen>
|
<screen>
|
||||||
$ cd wine
|
<prompt>$ </><userinput>cd wine</>
|
||||||
$ patch -p0 < ../patch_to_apply.diff
|
<prompt>$ </><userinput>patch -p0 <<replaceable>../patch_to_apply.diff</></>
|
||||||
</screen>
|
</screen>
|
||||||
|
</para>
|
||||||
<para>
|
<para>
|
||||||
To remove the patch, use the <parameter>-R</parameter> option:
|
To remove the patch, use the <parameter>-R</> option:
|
||||||
</para>
|
|
||||||
<screen>
|
<screen>
|
||||||
$ patch -p0 -R < ../patch_to_apply.diff
|
<prompt>$ </><userinput>patch -p0 -R <<replaceable>../patch_to_apply.diff</></>
|
||||||
</screen>
|
</screen>
|
||||||
|
</para>
|
||||||
<para>
|
<para>
|
||||||
If you want to do a test run to see if the patch will apply
|
If you want to do a test run to see if the patch will apply
|
||||||
successfully (e.g., if the patch was created from an older or
|
successfully (e.g., if the patch was created from an older or
|
||||||
newer version of the tree), you can use the
|
newer version of the tree), you can use the
|
||||||
<parameter>--dry-run</parameter> parameter to run the patch
|
<parameter>--dry-run</> parameter to run the patch
|
||||||
without writing to any files:
|
without writing to any files:
|
||||||
</para>
|
|
||||||
<screen>
|
<screen>
|
||||||
$ patch -p0 --dry-run < ../patch_to_apply.diff
|
<prompt>$ </><userinput>patch -p0 --dry-run <<replaceable>../patch_to_apply.diff</></>
|
||||||
</screen>
|
</screen>
|
||||||
|
</para>
|
||||||
<para>
|
<para>
|
||||||
<command>patch</command> is pretty smart about extracting
|
<command>patch</> is pretty smart about extracting
|
||||||
patches from the middle of a file, so if you save an email with
|
patches from the middle of a file, so if you save an email with
|
||||||
an inlined patch to a file on your hard drive, you can invoke
|
an inlined patch to a file on your hard drive, you can invoke
|
||||||
patch on it without stripping out the email headers and other
|
patch on it without stripping out the email headers and other
|
||||||
text. <command>patch</command> ignores everything that doesn't
|
text. <command>patch</> ignores everything that doesn't
|
||||||
look like a patch.
|
look like a patch.
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
The <parameter>-p0</parameter> option to <command>patch</command>
|
The <parameter>-p0</> option to <command>patch</>
|
||||||
tells it to keep the full file name from the patch file. For example,
|
tells it to keep the full file name from the patch file. For example,
|
||||||
if the file name in the patch file was
|
if the file name in the patch file was
|
||||||
<filename>wine/programs/clock/main.c</filename>.
|
<filename>wine/programs/clock/main.c</>.
|
||||||
Setting the <parameter>-p0</parameter> option would apply the patch
|
Setting the <parameter>-p0</> option would apply the patch
|
||||||
to the file of the same name i.e.
|
to the file of the same name i.e.
|
||||||
<filename>wine/programs/clock/main.c </filename>.
|
<filename>wine/programs/clock/main.c </>.
|
||||||
Setting the <parameter>-p1</parameter> option would strip off the
|
Setting the <parameter>-p1</> option would strip off the
|
||||||
first part of the file name and apply
|
first part of the file name and apply
|
||||||
the patch instead to <filename>programs/clock/main.c </filename>.
|
the patch instead to <filename>programs/clock/main.c </>.
|
||||||
The <parameter>-p1</parameter> option would be useful if you named
|
The <parameter>-p1</> option would be useful if you named
|
||||||
your top level wine directory differently to the person who sent you
|
your top level wine directory differently to the person who sent you
|
||||||
the patch. For the <parameter>-p1</parameter> option
|
the patch. For the <parameter>-p1</> option
|
||||||
<command>patch</command> should be run from the top level wine directory.
|
<command>patch</> should be run from the top level wine directory.
|
||||||
|
|
||||||
</para>
|
</para>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue