source: introduction/important/beyond.xml@ 563bc92

10.0 10.1 11.0 6.0 6.1 6.2 6.2.0 6.2.0-rc1 6.2.0-rc2 6.3 6.3-rc1 6.3-rc2 6.3-rc3 7.10 7.4 7.5 7.6 7.6-blfs 7.6-systemd 7.7 7.8 7.9 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind gnome kde5-13430 kde5-14269 kde5-14686 ken/refactor-virt krejzi/svn lazarus nosym perl-modules qt5new systemd-11177 systemd-13485 trunk v5_1 xry111/git-date xry111/git-date-for-trunk xry111/git-date-test
Last change on this file since 563bc92 was 563bc92, checked in by Bruce Dubbs <bdubbs@…>, 17 years ago

Misc grammar updates

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@2257 af4574ff-66df-0310-9fd7-8a98e5e911e0

  • Property mode set to 100644
File size: 4.4 KB
Line 
1<sect1 id="intro-important-beyond">
2<?dbhtml filename="beyond.html"?>
3<title>Going Beyond <acronym>BLFS</acronym></title>
4
5<para>The packages that are installed in this book are only the tip of the
6iceberg. We hope that the experience you gained with the <acronym>LFS</acronym>
7book and the <acronym>BLFS</acronym> book will give you the background needed
8to compile, install and configure packages that are not included in this book.
9</para>
10
11<para>When you want to install a package to a location other than
12<filename class='directory'>/</filename>, or <filename class='directory'>/usr</filename>, you are installing
13outside the default environment settings on most machines. The following
14examples should assist you in determining how to correct this situation.
15The examples cover the complete range of settings that may need
16updating, but they are not all needed in every situation.</para>
17
18<itemizedlist>
19<listitem><para>Expand the <envar>PATH</envar> to include
20<filename class='directory'>$PREFIX/bin</filename>.</para></listitem>
21<listitem><para>Expand the <envar>PATH</envar> for root to include
22<filename class='directory'>$PREFIX/sbin</filename>.</para></listitem>
23<listitem><para>Add <filename class='directory'>$PREFIX/lib</filename>
24to <filename>/etc/ld.so.conf</filename> or expand
25<envar>LD_LIBRARY_PATH</envar> to include it. Before using the latter option,
26check out <ulink url="http://www.visi.com/~barr/ldpath.html"/>. If you
27modify <filename>/etc/ld.so.conf</filename> remember to update
28<filename>/etc/ld.so.cache</filename> by executing <command>ldconfig</command>.</para></listitem>
29<listitem><para>Add <filename class='directory'>$PREFIX/man</filename>
30to <filename>/etc/man.conf</filename> or expand <envar>MANPATH</envar>.</para></listitem>
31<listitem><para>Add <filename class='directory'>$PREFIX/info</filename>
32to <envar>INFOPATH</envar>.</para></listitem>
33<listitem><para>Add <filename
34class='directory'>$PREFIX/lib/pkgconfig</filename> to
35<envar>PKG_CONFIG_PATH</envar>.</para></listitem>
36<listitem><para>Add <filename
37class='directory'>$PREFIX/include</filename> to <envar>CPPFLAGS</envar> when compiling packages
38that depend on the package you installed.</para></listitem>
39</itemizedlist>
40
41<para>If you are in search of a package that is not in the book, the following
42are different ways you can search for the concerned package.</para>
43
44<itemizedlist>
45
46<listitem><para>If you know the name of the package, then search FreshMeat for
47at <ulink url="http://freshmeat.net/"/>. Also search Google at
48<ulink url="http://google.com/"/>. Sometimes a search for the rpm at
49<ulink url="http://rpmfind.net/"/> or the deb at
50<ulink url="http://www.debian.org/distrib/packages#search_packages"/> can also
51lead to the website for the package.</para></listitem>
52
53<listitem><para>If you know the name of the executable, but not the package
54that the executable belongs to, first try a google search with the name of the
55executable. If the results are overwhelming, try searching for the given
56executable in the Debian repository at
57<ulink url="http://www.debian.org/distrib/packages#search_contents"/>.
58</para></listitem>
59
60</itemizedlist>
61
62<para>Some general hints on handling new packages:</para>
63
64<itemizedlist>
65
66<listitem><para>Many of the newer packages follow the <command>./configure
67&amp;&amp; make &amp;&amp; make install</command> <emphasis>dance</emphasis>
68routine. Help on the options accepted by configure can be obtained via the
69command <command>./configure --help</command>.</para></listitem>
70
71<listitem><para>Most of the packages contain documentation on compiling and
72installing the package. Some of the documents are excellent, some not so
73excellent. Check out the homepage of the package for any additional and updated
74hints for compiling and configuring the package.</para></listitem>
75
76<listitem><para>If you are having a problem compiling the package, try
77searching the lfs archives at <ulink url="http://search.linuxfromscratch.org/"/>
78for the error or if that fails try searching google. If everything else fails,
79try the blfs support mailing-list/news-server.</para></listitem>
80
81</itemizedlist>
82
83<tip><para>If you have found a package that is only available in .deb or .rpm
84format, there are two small scripts rpm2targz and deb2targz that are available
85at <ulink url="&downloads-root;/deb2targz.tar.bz2"/> and <ulink
86url="&downloads-root;/rpm2targz.tar.bz2"/> to convert the archives into a
87simple tar.gz format.</para></tip>
88
89</sect1>
Note: See TracBrowser for help on using the repository browser.