aboutsummaryrefslogtreecommitdiffstats
path: root/appendixa/introduction.xml
diff options
context:
space:
mode:
Diffstat (limited to 'appendixa/introduction.xml')
-rw-r--r--appendixa/introduction.xml25
1 files changed, 22 insertions, 3 deletions
diff --git a/appendixa/introduction.xml b/appendixa/introduction.xml
index 0214e633d..504699147 100644
--- a/appendixa/introduction.xml
+++ b/appendixa/introduction.xml
@@ -7,14 +7,16 @@ that is installed in this book:</para>
<itemizedlist>
+<listitem><para>The official download location for the
+package.</para></listitem>
+
<listitem><para>What the package contains.</para></listitem>
<listitem><para>What each program from a package does.</para></listitem>
-</itemizedlist>
+<listitem><para>What each package needs to compile.</para></listitem>
-<para>The packages are listed in the same order as they are installed in
-chapter 5 and chapter 6.</para>
+</itemizedlist>
<para>Most information about these packages (especially the descriptions of
them) come from the man pages from those packages. We are not going to print
@@ -33,5 +35,22 @@ of every package installed, but we can't do it without help.</para>
<para>Please note that currently only what a package does is described and not
why it needs to be installed. This may be added later.</para>
+<para>Also listed are all of the installation dependencies for all the
+packages that are installed in this book. The listings will include
+which programs from which packages are needed to successfully compile
+the package to be installed.</para>
+
+<para>These are not running dependencies, meaning they don't tell you
+what programs are needed to use that packages programs. Just the ones
+needed to compile it.</para>
+
+<para>The dependency list can be, from time to time, outdated in regards
+to the current used package version. Checking dependencies takes quite a
+bit of work, so they may lag behind a bit on the package update. But
+often with minor package updates, the installation dependencies hardly
+change, so they'll be current in most cases. If we upgrade to a major
+new release, we'll make sure the dependencies are checked too at the
+same time.</para>
+
</sect1>