[pkg-wine-party] [wine] 01/06: Update README.debian.
jreyer-guest at moszumanska.debian.org
Fri Feb 12 01:45:16 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.
Author: Jens Reyer <jre.winesim at gmail.com>
Date: Thu Feb 11 17:57:59 2016 +0100
Streamline line lengths, capitalization et al.
Add -development information if missing, and put it in brackets.
debian/README.debian | 72 ++++++++++++++++++++++++++++------------------------
1 file changed, 39 insertions(+), 33 deletions(-)
diff --git a/debian/README.debian b/debian/README.debian
index 103d4fb..02e3b76 100644
@@ -1,16 +1,13 @@
-If you have any problems, the Wine Troubleshooting Guide is often very useful:
+If you have any problems, the Wine FAQ is often very useful:
-The Wine FAQ may also be informative:
-Detailed documentation about Wine and it's internals are available in the
+Detailed documentation about Wine and its internals are available in the
various User Guides and manpages:
-For resources related to Debian wine packaging, please visit:
+For resources related to Debian Wine packaging, please visit:
To participate in development and/or discussion about the Debian packages,
@@ -18,15 +15,16 @@ please subscribe to the pkg-wine-party mailing list:
The Debian package repository can also be checked out with git:
-$ git clone git://anonscm.debian.org/pkg-wine/wine.git
+$ git clone https://anonscm.debian.org/git/pkg-wine/wine.git
Or viewed online at:
-Debugging information is no longer output by default. If you are interested in
-more verbose debugging output, you can set the WINEDEBUG environment variable.
+Debugging information is no longer output by default. If you are interested
+in more verbose debugging output, you can set the WINEDEBUG environment
$ WINEDEBUG=err+all wine
@@ -53,11 +51,12 @@ debsnap fetches source packages by default, which you will then need to build
Usually everything is automatically configured, but for fine-tuning a good tool
-is winecfg or winecfg-development.
+is winecfg (or winecfg-development).
If you need to set up Wine manually, without winecfg, you can force the
creation of a ~/.wine directory by running:
If something goes horribly wrong, you can always completely wipe your Wine
setup with "rm -rf ~/.wine". This will destroy everything you've installed,
@@ -66,21 +65,30 @@ please back it up first. You can then start fresh.
-Most Windows binaries are 32-bit applications. You need to install wine32 or
-wine32-development to run them. wine64 alone cannot do this.
+Most Windows binaries are 32-bit applications. You need to install wine32 (or
+wine32-development) to run them. wine64 (or wine64-development) alone cannot do
-On 64-bit systems you need to enable multiarch to install wine32 or
-wine32-development. As root, execute e.g.:
+On 64-bit systems you need to enable multiarch to install wine32 (or
+wine32-development). As root, execute e.g.:
# dpkg --add-architecture i386 && apt update && apt install wine32
+# dpkg --add-architecture i386 && apt update && apt install wine32-development
-If you have wine32 and wine64 installed Wine will default to a shared 64-bit
-wineprefix that runs (most) 32-bit Windows applications.
+If you have wine32 and wine64 (or wine32-development and wine64-development)
+installed, Wine will default to a shared 64-bit prefix that runs most 32-bit
-If this causes problems for an application you may create a 32-bit wineprefix
-by running e.g.:
+If this causes problems for an application, you may create a 32-bit prefix by
$ WINEARCH=win32 WINEPREFIX="$HOME/.wine32" wineboot
+$ WINEARCH=win32 WINEPREFIX="$HOME/.wine32" wineboot-development
+You have to specify this 32-bit prefix, whenever you want to use it, e.g.:
+$ WINEPREFIX="$HOME/.wine32" wine application.exe
+$ WINEPREFIX="$HOME/.wine32" wine-development application.exe
-If you don't want 64-bit at all, just uninstall wine64.
+If you don't want 64-bit at all, just uninstall wine64 (or
@@ -89,8 +97,8 @@ Instead libwine-gecko-* packages are available in the official Debian archives,
which provide Wine Gecko support.
Information about which Wine Gecko should be associated with any particular
-wine version is available at:
+Wine version is available at:
If the right libwine-gecko-*.deb package is not currently available, you can
manually extract an associated upstream WineGecko tarball to
@@ -99,16 +107,14 @@ 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:
+You can configure Wine to automatically launch Windows executables from the
+command line, for example:
-To configure backend support for that, you'll need to install the
-wine-binfmt package first and then execute:
+To configure backend support for that, you'll need to install the wine-binfmt
+package first and then execute:
$ sudo update-binfmts --import wine
-This change increases the risk of inadvertently launching Windows
-malware, so please make sure that you understand the security risks
-before blindly setting this up.
+This change increases the risk of inadvertently launching Windows malware, so
+please make sure that you understand the security risks before blindly setting
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