Here is my second patch to the Packaging Guide.
Changelog :
1.1 Added myself to authors section
1.2 Updated last revision date
1.3 some small updates
2.2 some small updates
Tom
Title: Document Revision Date
Index: documentation/packaging.sgml
===================================================================
RCS file: /opt/cvs-commit/wine/documentation/packaging.sgml,v
retrieving revision 1.10
diff -u -r1.10 packaging.sgml
--- documentation/packaging.sgml 13 Jan 2003 18:35:55 -0000 1.10
+++ documentation/packaging.sgml 16 Jan 2003 22:16:27 -0000
@@ -14,6 +14,8 @@
Updated by &name-andreas-mohr; &email-andreas-mohr;
+ Updated by &name-Tom-Wickline;
&email-tom-wickline;
+
@@ -31,7 +33,7 @@
documentation to include info about new features they implemented).
- This document was last revised on November 14, 2001.
+ This document was last revised on January 16, 2003.
@@ -55,11 +57,11 @@
PREFIX
PREFIX is the prefix used when selecting
- an installation target. The current default is /usr.
+ an installation target. The current default is /usr/local.
This results in binary installation into /usr/bin,
library installation into /usr/wine/lib, and so forth.
This value can be overridden by the packager.
- In fact, FHS 2.1
+ In fact, FHS 2.2
specifications suggest that a better
prefix is /opt/wine. Ideally, a packager would also
allow the installer to override this value.
@@ -71,7 +73,7 @@
ETCDIR is the prefix that Wine uses
to find the global configuration directory.
This can be changed by the configure option sysconfdir.
- The current default is /etc.
+ The current default is $prefix/etc.
@@ -219,11 +221,10 @@
A configuration file
- Wine will not run without a configuration file. Further,
- no default is currently provided by Wine. Some packagers may attempt
- to provide (or dynamically generate) a default configuration
- file. Some packagers may wish to
- rely on winesetup to generate the configuration file.
+ Wine will not run without a configuration file. Wine provides a
+ a sample config file and it can be found in /usr/share/doc/wine/samples.
+ Some packagers may attempt to provide (or dynamically generate) a default configuration
+ file. Some packagers may wish to rely on winesetup to generate the configuration file.
@@ -246,11 +247,13 @@
An initial set of registry entries.
- The current Wine standard is to use the regapi tool
+ The current Wine standard is to use the regedit tool
against the 'winedefault.reg' file to generate
a default registry.
-
+
+ The current preferred method of configuring/installing
+ Wine is to run /toos/wineinstall.
There are several other choices that could be made;
registries can be imported from a Windows partition.
At this time, Wine does not completely support
