Add information about prebuilt documentation packages in
other-than-sgml form.
This commit is contained in:
parent
096c1ae4ec
commit
0ee5f8c628
5
ANNOUNCE
5
ANNOUNCE
|
@ -24,7 +24,10 @@ from the following locations:
|
|||
ftp://orcus.progsoc.uts.edu.au/pub/Wine/development/Wine-20010216.tar.gz
|
||||
|
||||
It should also be available from any other site that mirrors ibiblio.org.
|
||||
For more download locations, see http://ftpsearch.lycos.com.
|
||||
For more download locations, see http://ftpsearch.lycos.com. These
|
||||
locations also hold pre-built documentation packages in various
|
||||
formats: wine-doc-html.tar.gz, wine-doc-txt.tar.gz, wine-doc.pdf.gz
|
||||
and wine-doc.ps.gz
|
||||
|
||||
You can also get the current source directly from the CVS tree. Check
|
||||
http://www.winehq.com/dev.html for details.
|
||||
|
|
9
README
9
README
|
@ -88,6 +88,9 @@ You also need flex version 2.5 or later and yacc.
|
|||
Bison will work as a replacement for yacc. If you are
|
||||
using RedHat or Debian, install the flex and bison packages.
|
||||
|
||||
In case you want to build the documentation yourself, you'll also
|
||||
need the DocBook tools (db2html, db2ps, db2pdf).
|
||||
|
||||
4. COMPILATION
|
||||
|
||||
In case you chose to not use wineinstall, run the following commands
|
||||
|
@ -121,6 +124,9 @@ Once Wine has been built correctly, you can do "make install"; this
|
|||
will install the wine executable, the Wine man page, and a few other
|
||||
needed files.
|
||||
|
||||
If you want to build the documentation, you can run "make" in the
|
||||
documentation directory.
|
||||
|
||||
Wine requires a configuration file named wine.conf. Its default
|
||||
location is /usr/local/etc, but you can supply a different name when
|
||||
configuring wine by using the --prefix or --sysconfdir options to
|
||||
|
@ -196,7 +202,8 @@ CVS: The current Wine development tree is available through CVS.
|
|||
Go to http://www.winehq.com/dev.shtml for more information.
|
||||
|
||||
If you add something, or fix a bug, please send a patch ('diff -u'
|
||||
format preferred) to julliard@winehq.com for inclusion in the next
|
||||
format preferred) to julliard@winehq.com or to the
|
||||
wine-patches@winehq.com mailing list for inclusion in the next
|
||||
release.
|
||||
|
||||
--
|
||||
|
|
|
@ -315,10 +315,12 @@ James Juran <jrj120@psu.edu>.
|
|||
.SH AVAILABILITY
|
||||
The most recent public version of
|
||||
.B wine
|
||||
can be obtained via FTP from ibiblio.org in the
|
||||
/pub/Linux/ALPHA/Wine/development directory. The releases are in the
|
||||
format 'Wine-yyyymmdd.tar.gz', or 'Wine-yyyymmdd.diff.gz' for the diff's
|
||||
from the previous release.
|
||||
can be obtained via FTP from ibiblio.org in the
|
||||
/pub/Linux/ALPHA/Wine/development directory. The releases are in the
|
||||
format 'Wine-yyyymmdd.tar.gz', or 'Wine-yyyymmdd.diff.gz' for the
|
||||
diff's from the previous release. The same directory holds the
|
||||
pre-built contents of the documentation in various formats
|
||||
(wine-doc.xxx.gz).
|
||||
.PP
|
||||
The latest snapshot of the code may be obtained via CVS. For information
|
||||
on how to do this, please see
|
||||
|
|
Loading…
Reference in New Issue