wwine 0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. data/COPYING +676 -0
  2. data/README +11 -0
  3. data/wwine +970 -0
  4. data/wwine.1 +198 -0
  5. metadata +64 -0
data/wwine.1 ADDED
@@ -0,0 +1,198 @@
1
+ .IX Title "WWINE 1"
2
+ .TH WWINE 1 "2010-04-14" "wwine 0.1" ""
3
+ .\" For nroff, turn off justification. Always turn off hyphenation; it makes
4
+ .\" way too many mistakes in technical documents.
5
+ .if n .ad l
6
+ .nh
7
+ .SH "NAME"
8
+ wwine \- a simple wine(1) wrapper
9
+ .SH "SYNOPSIS"
10
+ .IX Header "SYNOPSIS"
11
+ wwine \fI(\s-1WWINE\s0 \s-1PARAMETERS\s0)\fR \fI\s-1PROGRAM\s0\fR \*(-- \fI[\s-1PROGRAM\s0 \s-1ARGUMENTS\s0]\fR
12
+ .SH "DESCRIPTION"
13
+ .IX Header "DESCRIPTION"
14
+ \&\fBwwine\fR is a a \fIwine\fR\|(1) wrapper. It wraps various flavours of wine
15
+ (including vanilla wine and crossover office/games) into a single
16
+ unified interface, complete with full bottle support for all
17
+ of them (including vanilla wine).
18
+ .PP
19
+ It integrates well with all flavours, so for instance applications
20
+ installed using crossover will be manageable through the usual crossover
21
+ interface.
22
+ .PP
23
+ For vanilla wine it uses \s-1WINEPREFIX\s0 to achieve bottle support,
24
+ creating bottles as ~/.wwinebottles/[\s-1BOTTLE_NAME\s0].
25
+ .PP
26
+ When no \-\-wine is explicitly supplied, wwine will use wine, or if that is
27
+ not available, attempt to autodetect which flavour to use. See the information
28
+ for \-\-wine for more information.
29
+ .SH "OPTIONS"
30
+ .IX Header "OPTIONS"
31
+ .IP "\fB\-h, \-\-help\fR" 4
32
+ .IX Item "-h, --help"
33
+ Display the help screen
34
+ .IP "\fB\-w, \-\-wine\fR \fI\s-1FLAVOUR\s0\fR" 4
35
+ .IX Item "-w, --wine FLAVOUR"
36
+ Use the supplied flavour of wine. The default is to use vanilla wine.
37
+
38
+ Possible parameters: wine, cxgames, cxoffice, cedega, cxg (alias for cxgames),
39
+ cxo (alias for cxoffice) or /path/to/a/wine.binary
40
+
41
+ If this parameter is not supplied, wwine will attempt to autodetect which
42
+ wine to use, checking for the existance of flavours in the following order,
43
+ using the first one found: wine, cxgames, cxoffice, cedega. To see the
44
+ default flavour wwine will use, run \fIwwine \-\-debuginfo\fR.
45
+
46
+ See also \fI\-\-cxinstalldir\fR.
47
+ .IP "\fB\-b, \-\-bottle\fR \fI\s-1NAME\s0\fR" 4
48
+ .IX Item "-b, --bottle NAME"
49
+ Use the bottle with the name supplied. For cxgames, cxoffice or cedega
50
+ it uses the flavours builtin bottle support. For vanilla wine it sets
51
+ \&\s-1WINEPREFIX\s0 to use ~/.wwinebottles/<\s-1NAME\s0>. It defaults to no bottle,
52
+ in which case vanilla wine will use ~/.wine, cxoffice/cxgames will
53
+ use the bottle defined as default and for cedega a bottle named 'wwineFolder'
54
+ will be used.
55
+ .IP "\fB\-k, \-\-kill\fR" 4
56
+ .IX Item "-k, --kill"
57
+ Attempt to kill all running wine processes. See also \fI\-\-drykill\fR
58
+
59
+ The default signal is \s-1SIGTERM\s0, however you can supply any signal number
60
+ you want (ie. \*(L"wwine \-k9\*(R").
61
+ .IP "\fB\-\-drykill\fR" 4
62
+ .IX Item "--drykill"
63
+ Print what \fI\-\-kill\fR would have done, without actually doing anything.
64
+ .IP "\fB\-c, \-\-cxinstalldir\fR \fI\s-1PATH\s0\fR" 4
65
+ .IX Item "-c, --cxinstalldir PATH"
66
+ Use the supplied path as the path to either a crossover office/games install
67
+ directory, or as a directory that contains a cxoffice and/or cxgames directory.
68
+ .IP "\fB\-\-wrap\fR \fI\s-1PATH\s0\fR" 4
69
+ .IX Item "--wrap PATH"
70
+ Generate a wrapper script of the current command-line and write it to
71
+ \&\fI\s-1PATH\s0\fR. Simply write a wwine command as usual, and append \-\-wrap \fI\s-1PATH\s0\fR
72
+ to it, and wwine will generate a wrapper script that you can use to
73
+ run that command with at any later time so you don't have to remember
74
+ or retype it every time.
75
+
76
+ Generally \fI\s-1PATH\s0\fR should be somewhere in your \f(CW$PATH\fR (ie. ~/bin/somecommand)
77
+ so that you can start the command from anywhere.
78
+
79
+ By default the wrapper script will change directory to the directory
80
+ you were in when you created it, but you can use \fB\-\-wrapdir\fR to explicitly
81
+ supply one.
82
+
83
+ The wrapper script also contains some basic code that ensures that
84
+ even if you remove or move wwine, the wrapper script will keep working.
85
+ .IP "\fB\-\-wrapdir\fR \fI\s-1PATH\s0\fR" 4
86
+ .IX Item "--wrapdir PATH"
87
+ Change directory to \fI\s-1PATH\s0\fR in the wrapper script generated by \fI\-\-wrap\fR.
88
+ If this is not supplied wwine will change to the directory that you
89
+ were in at the time the wrapper script was created.
90
+ .IP "\fB\-s, \-\-from\fR \fI\s-1PATH\s0\fR" 4
91
+ .IX Item "-s, --from PATH"
92
+ Load parameters from the wwine wrapper script (as created by \fI\-\-wrap\fR)
93
+ located at \fI\s-1PATH\s0\fR. wwine will act as though the wrapper script had been
94
+ run, with one important difference, any additional command-line arguments
95
+ supplied to wwine wil override settings from the wrapper script.
96
+
97
+ This can be useful if you have a wrapper script set up to use cxgames,
98
+ but want to give a one off attempt at using wine. In such a case you could
99
+ do \*(L"wwine \-s /path/to/wrapperscript \-w wine\*(R".
100
+
101
+ This option is verbose, it will tell you each argument that is being
102
+ applied.
103
+ .IP "\fB\-v, \-\-verbose\fR" 4
104
+ .IX Item "-v, --verbose"
105
+ Increase verbosity. When this is present wwine will tell you the exact
106
+ commands it is running.
107
+ .IP "\fB\-\-man\fR" 4
108
+ .IX Item "--man"
109
+ Show the manpage. Normally 'man wwine' would do, but when wwine is
110
+ installed from a rubygem the wwine manpage isn't placed anywhere
111
+ in \fIman\fR\|(1)'s path, this will autodetect its location and issue man
112
+ directly on the wwine.1 file (and thus work even when 'man wwine'
113
+ does not).
114
+ .IP "\fB\-\-debuginfo\fR" 4
115
+ .IX Item "--debuginfo"
116
+ Output information that is useful for bug reports and to provide if you
117
+ need support.
118
+ .SH "EXAMPLES"
119
+ .IX Header "EXAMPLES"
120
+ .IP "\fIwwine file.exe\fR" 4
121
+ .IX Item "wwine file.exe"
122
+ The same as 'WINEDEBUG=\-all wine file.exe'
123
+ .IP "\fIwwine \-b file file.exe\fR" 4
124
+ .IX Item "wwine -b file file.exe"
125
+ Runs file.exe in wine, using the 'file' bottle.
126
+ .IP "\fIwwine \-w cxg \-b file file.exe\fR" 4
127
+ .IX Item "wwine -w cxg -b file file.exe"
128
+ Runs file.exe in crossover games using the cxgames 'file' bottle
129
+ .IP "\fIwwine \-\-cxinstalldir ~/cxgames7.0/ \-w cxg \-b file file.exe\fR" 4
130
+ .IX Item "wwine --cxinstalldir ~/cxgames7.0/ -w cxg -b file file.exe"
131
+ Runs file.exe in the version of crossover games that is installed at
132
+ \&\fI~/cxgames7.0\fR, using the cxgames 'file' bottle.
133
+
134
+ \&\-\-cxinstalldir can be useful to run something in a version of cxgames/cxoffice
135
+ other than your primary one. Ie. if a regression causes it to not run in a
136
+ later version.
137
+ .IP "\fIwwine \-w cxg \-b file file.exe \-\-wrap ~/bin/startFile\fR" 4
138
+ .IX Item "wwine -w cxg -b file file.exe --wrap ~/bin/startFile"
139
+ This causes wwine to create a wrapper shell script at ~/bin/startFile.
140
+ When you run that wrapper script, it will cd to the directory
141
+ you were in when the script was created, and issue a wwine command
142
+ with the above arguments. If you remove/uninstall wwine, the
143
+ wrapper script will most likely keep working as it has a fallback
144
+ that gets run if wwine cannot be found.
145
+
146
+ If you are not in the directory that you want wwine to run the file
147
+ from, you may use \-\-wrapdir to explicitly specify it.
148
+ .IP "\fIwwine \-s ~/bin/startFile \-w wine\fR" 4
149
+ .IX Item "wwine -s ~/bin/startFile -w wine"
150
+ This causes wwine to run the command specified in ~/bin/startFile
151
+ using the parameters specified in ~/bin/startFile, with the exception of
152
+ \&\-\-wine, which would be wine instead of cxgames (here assuming this
153
+ is the file created by the above example).
154
+ .IP "\fIwwine \-k\fR" 4
155
+ .IX Item "wwine -k"
156
+ Will make wwine attempt to kill all running wine processes on this system by
157
+ sending them the \s-1TERM\s0 signal.
158
+ .IP "\fIwwine \-k9\fR" 4
159
+ .IX Item "wwine -k9"
160
+ Will make wwine attempt to kill all running wine processes on this system by
161
+ sending them the \s-1KILL\s0 signal. Should only be used if \*(L"wwine \-k\*(R" fails.
162
+ .SH "DEPENDENCIES"
163
+ .IX Header "DEPENDENCIES"
164
+ Requires at least one of wine, cxoffice, cxgames or cedega.
165
+ .SH "ENVIRONMENT VARIABLES"
166
+ .IX Header "ENVIRONMENT VARIABLES"
167
+ .IP "\fB\s-1WWINE_VERBOSE\s0\fR" 4
168
+ .IX Item "WWINE_VERBOSE"
169
+ If this environment variable is set to the number '1' (ie. WWINE_VERBOSE=1) wwine
170
+ will act as if \-\-verbose was supplied. This is useful if you want to view verbose
171
+ output from a launch script you created with \-\-wrap.
172
+ .IP "\fB\s-1WINEDEBUG\s0\fR" 4
173
+ .IX Item "WINEDEBUG"
174
+ If this is not set, wwine will set it to \-all when using \-w wine.
175
+ .IP "\fB\s-1WINEPREFIX\s0\fR" 4
176
+ .IX Item "WINEPREFIX"
177
+ wwine uses the \s-1WINEPREFIX\s0 environment variable to add bottle support when
178
+ in \-w wine mode. If \s-1WINEPREFIX\s0 is set and a \-\-bottle is supplied, wwine will override
179
+ the existing \s-1WINEPREFIX\s0. If no bottle is supplied, wwine will respect \s-1WINEPREFIX\s0.
180
+ .PP
181
+ Any environment variables that wwine sets while it is running will be output
182
+ by wwine when in \-\-verbose mode.
183
+ .SH "HELP/SUPPORT"
184
+ .IX Header "HELP/SUPPORT"
185
+ If you need help or support please visit the website at <http://random.zerodogg.org/wwine>
186
+ .SH "BUGS AND LIMITATIONS"
187
+ .IX Header "BUGS AND LIMITATIONS"
188
+ If you find a bug, please report it at <http://random.zerodogg.org/wwine/bugs>. You may
189
+ submit feature requests there as well.
190
+ .SH "AUTHOR"
191
+ .IX Header "AUTHOR"
192
+ \&\fBwwine\fR is written by Eskild Hustvedt <\fIcode at zerodogg dot org\fR>
193
+ .SH "LICENSE AND COPYRIGHT"
194
+ .IX Header "LICENSE AND COPYRIGHT"
195
+ Copyright (C) Eskild Hustvedt 2009, 2010
196
+ .PP
197
+ This is free software; see the source for copying conditions. There is \s-1NO\s0
198
+ warranty; not even for \s-1MERCHANTABILITY\s0 or \s-1FITNESS\s0 \s-1FOR\s0 A \s-1PARTICULAR\s0 \s-1PURPOSE\s0.
metadata ADDED
@@ -0,0 +1,64 @@
1
+ --- !ruby/object:Gem::Specification
2
+ name: wwine
3
+ version: !ruby/object:Gem::Version
4
+ prerelease: false
5
+ segments:
6
+ - 0
7
+ - 1
8
+ version: "0.1"
9
+ platform: ruby
10
+ authors:
11
+ - Eskild Hustvedt
12
+ autorequire:
13
+ bindir: .
14
+ cert_chain: []
15
+
16
+ date: 2010-04-14 00:00:00 +02:00
17
+ default_executable:
18
+ dependencies: []
19
+
20
+ description: wwine is a simple wine wrapper.
21
+ email: code at zerodogg dot org
22
+ executables:
23
+ - wwine
24
+ extensions: []
25
+
26
+ extra_rdoc_files: []
27
+
28
+ files:
29
+ - wwine
30
+ - README
31
+ - COPYING
32
+ - wwine.1
33
+ has_rdoc: true
34
+ homepage: http://random.zerodogg.org/wwine
35
+ licenses: []
36
+
37
+ post_install_message:
38
+ rdoc_options: []
39
+
40
+ require_paths:
41
+ - lib
42
+ required_ruby_version: !ruby/object:Gem::Requirement
43
+ requirements:
44
+ - - ">="
45
+ - !ruby/object:Gem::Version
46
+ segments:
47
+ - 0
48
+ version: "0"
49
+ required_rubygems_version: !ruby/object:Gem::Requirement
50
+ requirements:
51
+ - - ">="
52
+ - !ruby/object:Gem::Version
53
+ segments:
54
+ - 0
55
+ version: "0"
56
+ requirements: []
57
+
58
+ rubyforge_project:
59
+ rubygems_version: 1.3.6
60
+ signing_key:
61
+ specification_version: 3
62
+ summary: wwine is a simple wine wrapper.
63
+ test_files: []
64
+