Changeset 8b354833
- Timestamp:
- 05/07/2005 11:38:51 AM (19 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 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, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 2625724e
- Parents:
- b3eff5b
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/important/beyond.xml
rb3eff5b r8b354833 7 7 8 8 <sect1 id="intro-important-beyond"> 9 <sect1info> 10 <othername>$LastChangedBy$</othername> 11 <date>$Date$</date> 12 </sect1info> 13 <?dbhtml filename="beyond.html"?> 14 <title>Going Beyond <acronym>BLFS</acronym></title> 9 <?dbhtml filename="beyond.html"?> 15 10 16 <para>The packages that are installed in this book are only the tip of the 17 iceberg. We hope that the experience you gained with the <acronym>LFS</acronym> 18 book and the <acronym>BLFS</acronym> book will give you the background needed 19 to compile, install and configure packages that are not included in this book. 20 </para> 11 <sect1info> 12 <othername>$LastChangedBy$</othername> 13 <date>$Date$</date> 14 </sect1info> 21 15 22 <para>When you want to install a package to a location other than 23 <filename class='directory'>/</filename>, or 24 <filename class='directory'>/usr</filename>, you are installing 25 outside the default environment settings on most machines. The following 26 examples should assist you in determining how to correct this situation. 27 The examples cover the complete range of settings that may need 28 updating, but they are not all needed in every situation.</para> 16 <title>Going Beyond BLFS</title> 29 17 30 <itemizedlist> 31 <listitem><para>Expand the <envar>PATH</envar> to include 32 <filename class='directory'>$PREFIX/bin</filename>.</para></listitem> 18 <para>The packages that are installed in this book are only the tip of the 19 iceberg. We hope that the experience you gained with the LFS book and 20 the BLFS book will give you the background needed to compile, install 21 and configure packages that are not included in this book.</para> 33 22 34 <listitem><para>Expand the <envar>PATH</envar> for root to include 35 <filename class='directory'>$PREFIX/sbin</filename>.</para></listitem> 23 <para>When you want to install a package to a location other than 24 <filename class='directory'>/</filename>, or 25 <filename class='directory'>/usr</filename>, you are installing 26 outside the default environment settings on most machines. The following 27 examples should assist you in determining how to correct this situation. 28 The examples cover the complete range of settings that may need 29 updating, but they are not all needed in every situation.</para> 36 30 37 <listitem><para>Add <filename class='directory'>$PREFIX/lib</filename> 38 to <filename>/etc/ld.so.conf</filename> or expand 39 <envar>LD_LIBRARY_PATH</envar> to include it. Before using the latter option, 40 check out <ulink url="http://www.visi.com/~barr/ldpath.html"/>. If you 41 modify <filename>/etc/ld.so.conf</filename>, remember to update 42 <filename>/etc/ld.so.cache</filename> by executing <command>ldconfig</command> 43 as the root user.</para></listitem> 31 <itemizedlist> 32 <listitem> 33 <para>Expand the <envar>PATH</envar> to include 34 <filename class='directory'>$PREFIX/bin</filename>.</para> 35 </listitem> 36 <listitem> 37 <para>Expand the <envar>PATH</envar> for 38 <systemitem class="username">root</systemitem> to include 39 <filename class='directory'>$PREFIX/sbin</filename>.</para> 40 </listitem> 41 <listitem> 42 <para>Add <filename class='directory'>$PREFIX/lib</filename> 43 to <filename>/etc/ld.so.conf</filename> or expand 44 <envar>LD_LIBRARY_PATH</envar> to include it. Before using the latter option, 45 check out <ulink url="http://www.visi.com/~barr/ldpath.html"/>. If you 46 modify <filename>/etc/ld.so.conf</filename>, remember to update 47 <filename>/etc/ld.so.cache</filename> by executing <command>ldconfig</command> 48 as the <systemitem class="username">root</systemitem> user.</para> 49 </listitem> 50 <listitem> 51 <para>Add <filename class='directory'>$PREFIX/man</filename> 52 to <filename>/etc/man.conf</filename> or expand <envar>MANPATH</envar>.</para> 53 </listitem> 54 <listitem> 55 <para>Add <filename class='directory'>$PREFIX/info</filename> 56 to <envar>INFOPATH</envar>.</para> 57 </listitem> 58 <listitem> 59 <para>Add <filename 60 class='directory'>$PREFIX/lib/pkgconfig</filename> to 61 <envar>PKG_CONFIG_PATH</envar>.</para> 62 </listitem> 63 <listitem> 64 <para>Add <filename class='directory'>$PREFIX/include</filename> to 65 <envar>CPPFLAGS</envar> when compiling packages that depend on 66 the package you installed.</para> 67 </listitem> 68 </itemizedlist> 44 69 45 <listitem><para>Add <filename class='directory'>$PREFIX/man</filename> 46 to <filename>/etc/man.conf</filename> or expand <envar>MANPATH</envar>.</para> 47 </listitem> 70 <para>If you are in search of a package that is not in the book, the following 71 are different ways you can search for the concerned package.</para> 48 72 49 <listitem><para>Add <filename class='directory'>$PREFIX/info</filename> 50 to <envar>INFOPATH</envar>.</para></listitem> 73 <itemizedlist> 74 <listitem> 75 <para>If you know the name of the package, then search FreshMeat for 76 it at <ulink url="http://freshmeat.net/"/>. Also search Google at 77 <ulink url="http://google.com/"/>. Sometimes a search for the rpm at 78 <ulink url="http://rpmfind.net/"/> or the deb at 79 <ulink url="http://www.debian.org/distrib/packages#search_packages"/> can also 80 lead to a link to the package.</para> 81 </listitem> 82 <listitem> 83 <para>If you know the name of the executable, but not the package 84 that the executable belongs to, first try a google search with the name of the 85 executable. If the results are overwhelming, try searching for the given 86 executable in the Debian repository at 87 <ulink url="http://www.debian.org/distrib/packages#search_contents"/>.</para> 88 </listitem> 89 </itemizedlist> 51 90 52 <listitem><para>Add <filename 53 class='directory'>$PREFIX/lib/pkgconfig</filename> to 54 <envar>PKG_CONFIG_PATH</envar>.</para></listitem> 91 <para>Some general hints on handling new packages:</para> 55 92 56 <listitem><para>Add <filename 57 class='directory'>$PREFIX/include</filename> to <envar>CPPFLAGS</envar> when 58 compiling packages that depend on the package you installed.</para></listitem> 59 </itemizedlist> 93 <itemizedlist> 94 <listitem> 95 <para>Many of the newer packages follow the <command>./configure 96 && make && make install</command> process. 97 Help on the options accepted by configure can be obtained via the 98 command <command>./configure --help</command>.</para> 99 </listitem> 100 <listitem> 101 <para>Most of the packages contain documentation on compiling and 102 installing the package. Some of the documents are excellent, some not so 103 excellent. Check out the homepage of the package for any additional and updated 104 hints for compiling and configuring the package.</para> 105 </listitem> 106 <listitem> 107 <para>If you are having a problem compiling the package, try 108 searching the lfs archives at <ulink url="http://search.linuxfromscratch.org/"/> 109 for the error or if that fails try searching Google. If everything else fails, 110 try the blfs-support mailing-list/news-group.</para> 111 </listitem> 112 </itemizedlist> 60 113 61 <para>If you are in search of a package that is not in the book, the following 62 are different ways you can search for the concerned package.</para> 63 64 <itemizedlist> 65 66 <listitem><para>If you know the name of the package, then search FreshMeat for 67 it at <ulink url="http://freshmeat.net/"/>. Also search Google at 68 <ulink url="http://google.com/"/>. Sometimes a search for the rpm at 69 <ulink url="http://rpmfind.net/"/> or the deb at 70 <ulink url="http://www.debian.org/distrib/packages#search_packages"/> can also 71 lead to a link to the package.</para></listitem> 72 73 <listitem><para>If you know the name of the executable, but not the package 74 that the executable belongs to, first try a google search with the name of the 75 executable. If the results are overwhelming, try searching for the given 76 executable in the Debian repository at 77 <ulink url="http://www.debian.org/distrib/packages#search_contents"/>. 78 </para></listitem> 79 80 </itemizedlist> 81 82 <para>Some general hints on handling new packages:</para> 83 84 <itemizedlist> 85 86 <listitem><para>Many of the newer packages follow the <command>./configure 87 && make && make install</command> process. 88 Help on the options accepted by configure can be obtained via the 89 command <command>./configure --help</command>.</para></listitem> 90 91 <listitem><para>Most of the packages contain documentation on compiling and 92 installing the package. Some of the documents are excellent, some not so 93 excellent. Check out the homepage of the package for any additional and updated 94 hints for compiling and configuring the package.</para></listitem> 95 96 <listitem><para>If you are having a problem compiling the package, try 97 searching the lfs archives at <ulink url="http://search.linuxfromscratch.org/"/> 98 for the error or if that fails try searching Google. If everything else fails, 99 try the blfs support mailing-list/news-server.</para></listitem> 100 101 </itemizedlist> 102 103 <tip><para>If you have found a package that is only available in .deb or .rpm 104 format, there are two small scripts, <command>rpm2targz</command> and 105 <command>deb2targz</command> that are available at 106 <ulink url="&downloads-project;/deb2targz.tar.bz2"/> and 107 <ulink url="&downloads-project;/rpm2targz.tar.bz2"/> to convert the archives 108 into a simple <filename>tar.gz</filename> format.</para></tip> 114 <tip> 115 <para>If you have found a package that is only available in .deb or .rpm 116 format, there are two small scripts, <command>rpm2targz</command> and 117 <command>deb2targz</command> that are available at 118 <ulink url="&downloads-project;/deb2targz.tar.bz2"/> and 119 <ulink url="&downloads-project;/rpm2targz.tar.bz2"/> to convert the archives 120 into a simple <filename>tar.gz</filename> format.</para> 121 </tip> 109 122 110 123 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.