[pkg-wine-party] [wine] 07/10: Update README.debian.
Jens Reyer
jreyer-guest at moszumanska.debian.org
Sat Jan 2 20:25:21 UTC 2016
This is an automated email from the git hooks/post-receive script.
jreyer-guest pushed a commit to branch master
in repository wine.
commit 2e7446434dc78fcf5735f1680e19d521ee12de23
Author: Jens Reyer <jre.winesim at gmail.com>
Date: Sat Jan 2 18:48:00 2016 +0100
Update README.debian.
---
debian/README.debian | 39 +++++++++++++++++++++++++++------------
1 file changed, 27 insertions(+), 12 deletions(-)
diff --git a/debian/README.debian b/debian/README.debian
index d645aa5..c68856f 100644
--- a/debian/README.debian
+++ b/debian/README.debian
@@ -1,6 +1,5 @@
Resources
=========
-
If you have any problems, the Wine Troubleshooting Guide is often very useful:
http://www.winehq.com/Trouble
@@ -24,22 +23,20 @@ $ git clone git://anonscm.debian.org/pkg-wine/wine.git
Or viewed online at:
http://anonscm.debian.org/gitweb/?p=pkg-wine/wine.git
-Debugging
-=========
-
-Debugging information is no longer output by default. If you are interested in
-more verbose debugging output, you can set the WINEDEBUG environment variable.
+Environment
+===========
+If you e.g. aren't interested in debugging output, you can set the WINEDEBUG
+environment variable to an empty value.
Examples:
-$ WINEDEBUG=all wine
-$ WINEDEBUG=all wine-development
+$ WINEDEBUG= wine
+$ WINEDEBUG= wine-development
-If you always want verbose information, you can include an
-"export WINEDEBUG=all" line in your ~/.bashrc file.
+If you never want debug information, you can include an "export WINEDEBUG="
+line in your ~/.bashrc file.
Old Versions
============
-
If you want to install a previous version of Wine, you should be able to fetch
prior Debian versions from:
http://snapshot.debian.org/package/wine
@@ -67,6 +64,25 @@ setup with "rm -rf ~/.wine". This will destroy everything you've installed,
including configuration and data files, so if you have anything important,
please back it up first. You can then start fresh.
+32-/64-bit
+==========
+Most Windows binaries are 32-bit applications. You need to install wine32 or
+wine32-development to run them. wine64 alone cannot do this.
+
+On 64-bit systems you need to enable multiarch to install wine32.
+As root, execute e.g.:
+ dpkg --add-architecture i386 && apt update && apt install wine32
+
+If you have wine32 and wine64 installed Wine will default to a shared 64-bit
+wineprefix that runs (most) 32-bit Windows applications.
+
+If this causes problems for an application you may create a 32-bit wineprefix
+by running e.g.:
+$ WINEARCH=win32 WINEPREFIX="$HOME/.wine32" wineboot
+
+If you don't want 64-bit at all, you may remove wine64 and install wine from a
+32-bit architecture (e.g. wine:i386).
+
Wine Gecko
==========
The downloader for Wine Gecko is intentionally disabled in the Debian packages.
@@ -84,7 +100,6 @@ the new Debian libwine-gecko-* package that is needed.
Automatically Launching Windows Executables
===========================================
-
You can configure wine to automatically launch Windows executables from
the command line, for example:
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-wine/wine.git
More information about the pkg-wine-party
mailing list