Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
wine
Manage
Activity
Members
Labels
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Package registry
Container Registry
Model registry
Operate
Terraform modules
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Yoann Laissus
wine
Commits
883bdc02
Commit
883bdc02
authored
24 years ago
by
John R. Sheets
Committed by
Alexandre Julliard
24 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Make SGML ID attributes in packaging.sgml more unique to avoid
conflicts when we bundle all four guides into a single set.
parent
a234db82
No related branches found
Branches containing commit
Tags
wine-980118
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
documentation/packaging.sgml
+19
-19
19 additions, 19 deletions
documentation/packaging.sgml
with
19 additions
and
19 deletions
documentation/packaging.sgml
+
19
−
19
View file @
883bdc02
...
...
@@ -3,7 +3,7 @@
<chapter id="pkg-preface"> <title>Preface</title>
<sect1 id="
A
uthors"> <title>Authors</title>
<sect1 id="
pkg-a
uthors"> <title>Authors</title>
<para>
Written by &name-marcus-meissner; <email>&email-marcus-meissner;</email>
...
...
@@ -11,7 +11,7 @@
</para>
</sect1>
<sect1 id="
D
ate"> <title>Document Revision Date</title>
<sect1 id="
pkg-d
ate"> <title>Document Revision Date</title>
<para>
...
...
@@ -24,7 +24,7 @@
</sect1>
<sect1 id="
T
erms"> <title>Terms used in this document</title>
<sect1 id="
pkg-t
erms"> <title>Terms used in this document</title>
<para>There are several terms and paths used in this
document as place holders for configurable values.
...
...
@@ -116,7 +116,7 @@
that have been considered and their rationales.
</para>
<sect1 id="
G
oals"> <title>Goals</title>
<sect1 id="
pkg-g
oals"> <title>Goals</title>
<para>
An installation from a Wine pacakage should:
</para>
...
...
@@ -194,7 +194,7 @@
</sect1>
<sect1 id="
R
equirements"> <title>Requirements</title>
<sect1 id="
pkg-r
equirements"> <title>Requirements</title>
<para>
Successfully installing Wine requires:
</para>
...
...
@@ -268,13 +268,13 @@
<chapter id="
C
omponents"><title>Wine Components</title>
<chapter id="
pkg-c
omponents"><title>Wine Components</title>
<para>
This section lists all files that pertain to Wine.
</para>
<sect1 id=static><title>Wine Static and Shareable Files</title>
<sect1 id=
"pkg-
static
"
><title>Wine Static and Shareable Files</title>
<para>
At the time of this writing, the following components
...
...
@@ -646,7 +646,7 @@
</sect1>
<sect1 id=nonstatic><title>Dynamic Wine Files</title>
<sect1 id=
"pkg-
nonstatic
"
><title>Dynamic Wine Files</title>
<para>
Wine also generates and depends on a number of dynamic
...
...
@@ -700,7 +700,7 @@
</para>
<para>
This debate is addressed more completely
below, in <link linkend=strategy endterm=strategy.id></link>.
below, in <link linkend=
pkg-
strategy endterm=strategy.id></link>.
</para>
</listitem>
</varlistentry>
...
...
@@ -860,7 +860,7 @@
</sect1>
<sect1 id=winpartition><title>Important Files from a Windows Partition</title>
<sect1 id=
"pkg-
winpartition
"
><title>Important Files from a Windows Partition</title>
<para>
Wine has the ability to use files from an installation of the
actual Microsoft Windows operating system. Generally these
...
...
@@ -924,7 +924,7 @@
</chapter>
<chapter id=strategy><title id=strategy.id>Packaging Strategies</title>
<chapter id=
"pkg-
strategy
"
><title id=strategy.id>Packaging Strategies</title>
<para>
There has recently been a lot of discussion on the Wine
...
...
@@ -939,7 +939,7 @@
advocated on the mailing list.
</para>
<sect1 id=whatfiles><title>Distribution of Wine into packages</title>
<sect1 id=
"pkg-
whatfiles
"
><title>Distribution of Wine into packages</title>
<para>
The most basic question to ask is given the Wine CVS tree,
what physical files are you, the packager, going to produce?
...
...
@@ -954,7 +954,7 @@
</para>
</sect1>
<sect1 id=wherefiles><title>Where to install files</title>
<sect1 id=
"pkg-
wherefiles
"
><title>Where to install files</title>
<para>
This question is not really contested. It will vary
by distribution, and is really up to the packager.
...
...
@@ -1019,7 +1019,7 @@
</sect1>
<sect1 id=whattomake><title>What files to create</title>
<sect1 id=
"pkg-
whattomake
"
><title>What files to create</title>
<para>
After installing the static and shareable files, the next
question the packager needs to ask is how much dynamic
...
...
@@ -1114,7 +1114,7 @@
</sect1>
<sect1 id=wineconf><title>What to put into the wine config file</title>
<sect1 id=
"pkg-
wineconf
"
><title>What to put into the wine config file</title>
<para>
The next hard question is what the Wine config should look like.
The current best practices seems to involve using drives from M to Z.
...
...
@@ -1128,9 +1128,9 @@
<chapter id="pkg-
I
mplementation"> <title>Implementation</title>
<chapter id="pkg-
i
mplementation"> <title>Implementation</title>
<sect1 id=
O
pen
L
inux><title>OpenLinux Sample</title>
<sect1 id=
"pkg-o
pen
l
inux
"
><title>OpenLinux Sample</title>
<orderedlist inheritnum="inherit">
<listitem>
...
...
@@ -1754,7 +1754,7 @@ Startup=
</chapter>
<chapter id=todo><Title>Work to be done</title>
<chapter id=
"pkg-
todo
"
><Title>Work to be done</title>
<para>
In preparing this document, it became clear that there were
...
...
@@ -1864,6 +1864,6 @@ Startup=
<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-parent-document:("wine-doc.sgml" "
set" "book
" "chapter" "")
sgml-parent-document:("wine-doc.sgml" "
book" "part
" "chapter" "")
End:
-->
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment