|
@@ -2,6 +2,9 @@
|
|
<title>About dependencies</title>
|
|
<title>About dependencies</title>
|
|
<?dbhtml filename="aboutdependencies.html" dir="chapter02"?>
|
|
<?dbhtml filename="aboutdependencies.html" dir="chapter02"?>
|
|
|
|
|
|
|
|
+<!-- Leave this file in the repo until we figure out finally what to do with
|
|
|
|
+dependencies -->
|
|
|
|
+
|
|
<para>There are a few ways to compile a list of a package's installation
|
|
<para>There are a few ways to compile a list of a package's installation
|
|
dependencies. What we consider the best way is using the
|
|
dependencies. What we consider the best way is using the
|
|
<command>strace</command> program available at <ulink
|
|
<command>strace</command> program available at <ulink
|
|
@@ -44,7 +47,7 @@ can't simply ignore all autoconf entries. A manual validation really is a
|
|
requirement for an accurate list.</para>
|
|
requirement for an accurate list.</para>
|
|
|
|
|
|
<para>This book is not so verbose as to list exactly which program from which
|
|
<para>This book is not so verbose as to list exactly which program from which
|
|
-package is required for a successfull installation (we used to, but it had
|
|
|
|
|
|
+package is required for a successful installation (we used to, but it had
|
|
become too much work to maintain it). The book will contain simply the
|
|
become too much work to maintain it). The book will contain simply the
|
|
names of packages you need to have installed. If you need the verbosity
|
|
names of packages you need to have installed. If you need the verbosity
|
|
in the form of "package a needs file b and c from package d", have a look
|
|
in the form of "package a needs file b and c from package d", have a look
|