Ticket #7134: cleaning_files.patch
File cleaning_files.patch, 26.8 KB (added by , 8 years ago) |
---|
-
kde/phonon-backend-vlc.xml
32 32 <para>This package provides a <application>Phonon</application> backend 33 33 which utilizes the <application>VLC</application> media framework. Its 34 34 library is used by both KDE4 and KF5, but they must be linked to <xref 35 linkend= 'qt4'/> and <xref linkend='qt5'/> respectively. The two versions do35 linkend="qt4"/> and <xref linkend="qt5"/> respectively. The two versions do 36 36 not conflict with each other.</para> 37 37 38 38 &lfs78_checked; -
kde/libdbusmenuqt.xml
32 32 <para>This library provides a <application>Qt</application> implementation 33 33 of the DBusMenu specification that exposes menus via DBus. Its 34 34 libraries are used by both KDE4 and KF5, but they must be linked to <xref 35 linkend= 'qt4'/> and <xref linkend='qt5'/> respectively. The two versions do35 linkend="qt4"/> and <xref linkend="qt5"/> respectively. The two versions do 36 36 not conflict with each other. </para> 37 37 38 38 &lfs78_checked; -
kde/polkit-qt.xml
31 31 32 32 <para><application>Polkit-Qt</application> provides an API to PolicyKit in 33 33 the Qt environment. Its libraries are used by both KDE4 and KF5, but they 34 must be linked to <xref linkend= 'qt4'/> and <xref linkend='qt5'/>34 must be linked to <xref linkend="qt4"/> and <xref linkend="qt5"/> 35 35 respectively. The two versions do not conflict with each other. </para> 36 36 37 37 &lfs78_checked; -
server/mail/sendmail.xml
194 194 definitions.</para> 195 195 196 196 <para><command>sed ... include/sm/bdb.h</command>: This allows sendmail to 197 build properly with <xref linkend= 'db'/> versions 5 and above.</para>197 build properly with <xref linkend="db"/> versions 5 and above.</para> 198 198 199 199 <para><command>sh Build; sh Build sendmail.cf; sh Build install-cf; 200 200 sh Build install</command>: <application>sendmail</application> uses an -
multimedia/libdriv/frei0r.xml
72 72 73 73 <bridgehead renderas="sect4">Required</bridgehead> 74 74 <para> 75 <xref linkend= 'gavl'/> and76 <xref linkend= 'opencv'/>75 <xref linkend="gavl"/> and 76 <xref linkend="opencv"/> 77 77 </para> 78 78 79 79 <bridgehead renderas="sect4">Optional</bridgehead> 80 80 <para> 81 <xref linkend= 'doxygen'/>81 <xref linkend="doxygen"/> 82 82 </para> 83 83 84 84 <para condition="html" role="usernotes">User Notes: -
multimedia/libdriv/mlt.xml
63 63 64 64 <bridgehead renderas="sect4">Required</bridgehead> 65 65 <para> 66 <xref linkend= 'frei0r'/> and67 <xref linkend= 'qt5'/>66 <xref linkend="frei0r"/> and 67 <xref linkend="qt5"/> 68 68 </para> 69 69 70 70 <bridgehead renderas="sect4">Optional</bridgehead> 71 71 <para> 72 <xref linkend= 'doxygen'/>,72 <xref linkend="doxygen"/>, 73 73 <xref linkend="libexif"/>, 74 74 <xref linkend="sdl"/>, 75 75 <ulink url="http://jackaudio.org">JACK</ulink>, -
multimedia/libdriv/xine-lib.xml
69 69 <xref linkend="x-window-system"/>, 70 70 <xref linkend="ffmpeg"/>, and at least one of: 71 71 <xref linkend="alsa"/>, 72 <xref linkend= 'pulseaudio'/> or72 <xref linkend="pulseaudio"/> or 73 73 <ulink url="http://jackaudio.org/">JACK</ulink> 74 74 </para> 75 75 -
multimedia/libdriv/libsamplerate.xml
61 61 62 62 <bridgehead renderas="sect4">Optional</bridgehead> 63 63 <para role="optional"> 64 <xref linkend= 'libsndfile'/>, and64 <xref linkend="libsndfile"/>, and 65 65 <ulink url="http://www.fftw.org/">libfftw3</ulink> (for tests) 66 66 </para> 67 67 -
multimedia/libdriv/libao.xml
68 68 <para role="optional"> 69 69 <xref linkend="x-window-system"/>, 70 70 <xref linkend="alsa"/>, and 71 <xref linkend= 'pulseaudio'/>71 <xref linkend="pulseaudio"/> 72 72 </para> 73 73 74 74 <para condition="html" role="usernotes">User Notes: -
multimedia/libdriv/gst10-plugins-good.xml
110 110 <xref linkend="speex"/>, 111 111 <xref linkend="taglib"/>, 112 112 <xref linkend="valgrind"/>, 113 <xref linkend= 'v4l-utils'/>,113 <xref linkend="v4l-utils"/>, 114 114 <ulink url="http://jackaudio.org/">JACK</ulink>, 115 115 <ulink url="http://caca.zoy.org/wiki/libcaca">libcaca</ulink>, 116 116 <ulink url="http://sourceforge.net/projects/libraw1394/">libiec61883</ulink>, -
multimedia/libdriv/libcanberra.xml
90 90 <para role="optional"> 91 91 <xref linkend="gtk2"/>, 92 92 <xref linkend="gtk-doc"/>, 93 <xref linkend= 'pulseaudio'/> and93 <xref linkend="pulseaudio"/> and 94 94 <ulink url="http://tdb.samba.org/">tdb</ulink> 95 95 </para> 96 96 -
multimedia/libdriv/gavl.xml
64 64 65 65 <bridgehead renderas="sect4">Required</bridgehead> 66 66 <para> 67 <xref linkend= 'libpng'/>67 <xref linkend="libpng"/> 68 68 </para> 69 69 70 70 <bridgehead renderas="sect4">Optional</bridgehead> 71 71 <para> 72 <xref linkend= 'doxygen'/>72 <xref linkend="doxygen"/> 73 73 </para> 74 74 75 75 <para condition="html" role="usernotes">User Notes: -
xsoft/other/balsa.xml
94 94 95 95 <bridgehead renderas="sect4">Optional to Build S/MIME Support</bridgehead> 96 96 <para role="optional"> 97 <xref linkend= 'gpgme'/>97 <xref linkend="gpgme"/> 98 98 </para> 99 99 100 100 <para condition="html" role="usernotes">User Notes: -
postlfs/virtualization/qemu.xml
132 132 <para>The Intel or AMD settings are not both required, but the one matching 133 133 your system processor is required.</para> 134 134 135 <para>For networking, check that <xref linkend= 'bridgeutils'/> is installed135 <para>For networking, check that <xref linkend="bridgeutils"/> is installed 136 136 and the following options in the kernel configuration are enabled:</para> 137 137 138 138 <screen><literal>[*] Networking support ---> [CONFIG_NET] … … 283 283 284 284 <itemizedlist spacing="compact"> 285 285 <listitem> 286 <para>Set up bridging with <xref linkend= 'bridgeutils'/>.</para>286 <para>Set up bridging with <xref linkend="bridgeutils"/>.</para> 287 287 </listitem> 288 288 289 289 <listitem> -
postlfs/config/firmware.xml
200 200 201 201 <para>If the microcode was not updated, there is no new microcode for 202 202 this system's processor. If it did get updated, you can now proceed to <xref 203 linkend= 'early-microcode'/>.</para>203 linkend="early-microcode"/>.</para> 204 204 205 205 </sect3> 206 206 … … 238 238 239 239 <para>If the microcode was not updated, there is no new microcode for 240 240 this system's processor. If it did get updated, you can now proceed to <xref 241 linkend= 'early-microcode'/>.</para>241 linkend="early-microcode"/>.</para> 242 242 243 243 </sect3> 244 244 … … 247 247 248 248 <para>If you have established that updated microcode is available for 249 249 your system, it is time to prepare it for early loading. This requires 250 an additional package, <xref linkend= 'cpio'/>, as well as changes to250 an additional package, <xref linkend="cpio"/>, as well as changes to 251 251 the kernel config and the creation of an initrd which will need to be 252 252 added to grub.cfg.</para> 253 253 … … 360 360 large modern system you can probably spare the space, but it is still 361 361 redundant to install all the unused files each time you build a system.</para> 362 362 363 <para>A better approach is to install <xref linkend= 'pciutils'/> and then363 <para>A better approach is to install <xref linkend="pciutils"/> and then 364 364 use <userinput>lspci</userinput> to identify which VGA controller is 365 365 installed.</para> 366 366 … … 428 428 <title>Firmware for Other Devices</title> 429 429 430 430 <para> Identifying the correct firmware will typically require you to 431 install <xref linkend= 'pciutils'/>, and then use431 install <xref linkend="pciutils"/>, and then use 432 432 <userinput>lspci</userinput> to identify the device. You should then search 433 433 online to check which module it uses, which firmware, and where to obtain 434 434 the firmware — not all of it is in linux-firmware.</para> 435 435 436 436 <para>If possible, you should begin by using a wired connection when you 437 437 first boot your LFS system. To use a wireless connection you will need to 438 use a network tools such as <xref linkend= 'wireless_tools'/> and <xref439 linkend= 'wpa_supplicant'/>.</para>438 use a network tools such as <xref linkend="wireless_tools"/> and <xref 439 linkend="wpa_supplicant"/>.</para> 440 440 441 441 <para>Firmware may also be needed for other devices such as some SCSI 442 442 controllers, bluetooth adaptors, or TV recorders. The same principles -
postlfs/config/devices.xml
125 125 126 126 <note><para>The above line is used for descriptive purposes only. The 127 127 scanner <application>udev</application> rules are put into place when 128 installing <xref linkend= 'sane'/>.</para></note>128 installing <xref linkend="sane"/>.</para></note> 129 129 130 130 </sect2> 131 131 -
postlfs/filesystems/aboutlvm.xml
24 24 <para>A complete discussion of LVM is beyond the scope of this introduction, 25 25 but basic concepts are presented below.</para> 26 26 27 <para>To run any of the commands presented here, the <xref linkend= 'lvm2'/>27 <para>To run any of the commands presented here, the <xref linkend="lvm2"/> 28 28 package must be installed. All commands must be run as the <systemitem 29 29 class="username">root</systemitem> user.</para> 30 30 … … 88 88 lvcreate --name home --size 500G lfs-lvm</userinput></screen> 89 89 90 90 <para>Finally the logical volumes can be formatted and mounted. In this 91 example, the jfs file system (<xref linkend= 'jfsutils'/>) is used for91 example, the jfs file system (<xref linkend="jfsutils"/>) is used for 92 92 demonstration purposes.</para> 93 93 94 94 <screen><userinput>mkfs -t ext4 /dev/lfs-lvm/home -
postlfs/filesystems/aboutraid.xml
30 30 <para>Note that while RAID provides protection against disk 31 31 failures, it is not a substitute for backups. A file deleted 32 32 is still deleted on all the disks of a RAID array. Modern backups 33 are generally done via <xref linkend= 'rsync'/>.</para>33 are generally done via <xref linkend="rsync"/>.</para> 34 34 35 35 <para>There are three major types of RAID implementation: 36 36 Hardware RAID, BIOS-based RAID, and Software RAID.</para> … … 78 78 <para>Software based RAID is the most flexible form of RAID. It is 79 79 easy to install and update and provides full capability on all or 80 80 part of any drives available to the system. In BLFS, the RAID software 81 is found in <xref linkend= 'mdadm'/>.</para>81 is found in <xref linkend="mdadm"/>.</para> 82 82 83 83 <para>Configuring a RAID device is straight forward using 84 84 <application>mdadm</application>. Generally devices are created in the … … 87 87 </para> 88 88 89 89 <para>The first step in creating a RAID array is to use partitioning software 90 such as <userinput>fdisk</userinput> or <xref linkend= 'parted'/> to define the90 such as <userinput>fdisk</userinput> or <xref linkend="parted"/> to define the 91 91 partitions needed for the array. Usually, there will be one partition on 92 92 each drive participating in the RAID array, but that is not strictly necessary. 93 93 For this example, there will be four disk drives: … … 161 161 1 8 17 1 active sync /dev/sdb1</literal></screen> 162 162 163 163 <para>From this point, the partitions can be formated with the filesystem of 164 choice (e.g. ext3, ext4, <xref linkend= 'xfsprogs'/>, <xref linkend='reiserfs'/>,164 choice (e.g. ext3, ext4, <xref linkend="xfsprogs"/>, <xref linkend="reiserfs"/>, 165 165 etc). The formatted partitions can then be mounted. The 166 166 <filename>/etc/fstab</filename> ifile can use the devices created for mounting at 167 167 boot time and the linux command line in -
postlfs/filesystems/lvm2.xml
77 77 78 78 <bridgehead renderas="sect4">Optional</bridgehead> 79 79 <para role="optional"> 80 <xref linkend= 'mdadm'/>,81 <xref linkend= 'reiserfs'/>,82 <xref linkend= 'valgrind'/>,83 <xref linkend= 'which'/>,84 <xref linkend= 'xfsprogs'/> (all five may be used, but are not required,80 <xref linkend="mdadm"/>, 81 <xref linkend="reiserfs"/>, 82 <xref linkend="valgrind"/>, 83 <xref linkend="which"/>, 84 <xref linkend="xfsprogs"/> (all five may be used, but are not required, 85 85 for tests), and 86 86 <ulink url='https://github.com/jthornber/thin-provisioning-tools'> 87 87 thin-provisioning-tools</ulink> -
postlfs/security/openssl.xml
194 194 <para> 195 195 Most users will want to install Certificate Authority Certificates 196 196 for validation of downloaded certificates. For example, these 197 certificates can be used by <xref linkend= 'git'/>,198 <xref linkend= 'curl'/> or <xref linkend='wget'/> when accessing secure197 certificates can be used by <xref linkend="git"/>, 198 <xref linkend="curl"/> or <xref linkend="wget"/> when accessing secure 199 199 (https protocol) sites. To do this, follow the instructions from the 200 <xref linkend= 'cacerts'/> page.200 <xref linkend="cacerts"/> page. 201 201 </para> 202 202 203 203 <para> -
postlfs/security/cacerts.xml
26 26 Linux system. In order for a certificate to be trusted, it must be signed by 27 27 a trusted agent called a Certificate Authority (CA). The certificates loaded 28 28 by this section are from the list on the Mozilla version control system and 29 formats it into a form used by <xref linkend= 'openssl'/>. The certificates29 formats it into a form used by <xref linkend="openssl"/>. The certificates 30 30 can also be used by other applications either directly of indirectly through 31 31 <application>openssl</application>.</para> 32 32 … … 331 331 <screen><userinput>rm -r certs BLFS-ca-bundle*</userinput></screen> 332 332 333 333 <para>After installing or updating certificates, if OpenJDK is installed, 334 update the certificates for Java using the procedures at <xref linkend= 'ojdk-certs'/>.</para>334 update the certificates for Java using the procedures at <xref linkend="ojdk-certs"/>.</para> 335 335 336 336 337 337 </sect2> -
pst/typesetting/tex-path.xml
17 17 18 18 <para>Before starting to build TeX Live, set up your PATH so 19 19 that the system can properly find the files. If you set up your login 20 scripts as recommended in <xref linkend= 'postlfs-config-profile'/>, update20 scripts as recommended in <xref linkend="postlfs-config-profile"/>, update 21 21 the needed paths by appending to the 22 22 <filename>extrapaths.sh</filename> script. The programs are always 23 23 installed in an <ARCH>-linux subdirectory and on 32-bit x86 this is -
x/installing/xorg-config.xml
36 36 37 37 <para>Generally, there is no specific configuration required for 38 38 <application>Xorg</application>, but customization is possible. For details 39 see <xref linkend= 'xconfig'/> below.</para>39 see <xref linkend="xconfig"/> below.</para> 40 40 41 41 </sect2> 42 42 -
x/installing/mesa.xml
104 104 105 105 <bridgehead renderas="sect4">Optional</bridgehead> 106 106 <para role="optional"> 107 <xref linkend="wayland"/> (required for <xref linkend= 'plasma5-build'/>),107 <xref linkend="wayland"/> (required for <xref linkend="plasma5-build"/>), 108 108 <ulink url="ftp://ftp.freedesktop.org/pub/mesa/demos/">mesa-demos</ulink> 109 109 (provides more than 300 extra demos to test 110 110 <application>Mesa</application>; this includes the same programs … … 149 149 150 150 <note> 151 151 <para>Add wayland to the <option>--with-egl-platforms</option> option 152 below if you plan on building <xref linkend= 'plasma5-build'/>.</para>152 below if you plan on building <xref linkend="plasma5-build"/>.</para> 153 153 </note> 154 154 155 155 <screen><userinput>GLL_DRV="nouveau,r300,r600,radeonsi,svga,swrast" && -
x/installing/libevdev.xml
123 123 make</userinput></screen> 124 124 125 125 <para> 126 If you have the optional <xref linkend= 'check'/> package installed, the126 If you have the optional <xref linkend="check"/> package installed, the 127 127 regression tests can be run as the <systemitem 128 128 class="username">root</systemitem> user with <command>make 129 129 check</command>, in a graphical session. One test shuts down and locks -
x/installing/xorg7.xml
132 132 133 133 <note><para>If you've decided to use the standard <filename 134 134 class="directory">/usr</filename> prefix, you can omit the remainder of 135 this page and continue at <xref linkend= 'util-macros'/>.</para></note>135 this page and continue at <xref linkend="util-macros"/>.</para></note> 136 136 137 137 <para>If you've decided to <emphasis>not</emphasis> use the standard 138 138 prefix, be sure to add <filename -
x/lib/qt4.xml
432 432 EOF</userinput></screen> 433 433 434 434 <para> 435 Some packages such as <xref linkend= 'vlc'/> look for certain435 Some packages such as <xref linkend="vlc"/> look for certain 436 436 executables with a -qt4 suffix. Run the following command as the 437 437 <systemitem class="username">root</systemitem> user 438 438 to create the necessary symlinks: -
x/lib/qt5.xml
353 353 EOF</userinput></screen> 354 354 355 355 <para> 356 Some packages such as <xref linkend= 'vlc'/> look for certain356 Some packages such as <xref linkend="vlc"/> look for certain 357 357 executables with a -qt5 suffix. Run the following command as the 358 358 <systemitem class="username">root</systemitem> user 359 359 to create the necessary symlinks: -
general/graphlib/gegl.xml
167 167 href="../../xincludes/gtk-doc-rebuild.xml"/> 168 168 169 169 <para> 170 <envar>LC_ALL=en_US</envar>: In some locales with <xref linkend= 'ruby'/>170 <envar>LC_ALL=en_US</envar>: In some locales with <xref linkend="ruby"/> 171 171 installed, one build component fails and prevents completion of the 172 172 procedure. Using this variable avoids the problem. 173 173 </para> -
general/sysutils/logrotate.xml
231 231 non-existing errors appear, when some intermediate files are expected, 232 232 because they are not actually created.</para> 233 233 234 <para>To set up <xref linkend= 'fcron'/> to run234 <para>To set up <xref linkend="fcron"/> to run 235 235 <command>logrotate ...</command> at 3AM daily, root's crontab should be 236 236 edited to add:</para> 237 237 -
general/prog/ojdk-conf.xml
18 18 <para> 19 19 After the package installation is complete, the next step is to make sure 20 20 that the system can properly find the files. If you set up your login 21 scripts as recommended in <xref linkend= 'postlfs-config-profile'/>, update21 scripts as recommended in <xref linkend="postlfs-config-profile"/>, update 22 22 the environment by creating the <filename>openjdk.sh</filename> script, 23 23 as the <systemitem class="username">root</systemitem> user: 24 24 </para> -
archive/kde/core/config.xml
73 73 <para>Set the paths. Thee are several ways to do this. You can edit 74 74 <filename>/etc/profile</filename>, or <filename>~/.bash_/profile</filename> 75 75 to add the paths. If you used the recommended procedure in <xref 76 linkend= 'postlfs-config-profile'/>, run the following as the <systemitem76 linkend="postlfs-config-profile"/>, run the following as the <systemitem 77 77 class="username">root</systemitem> user:</para> 78 78 79 79 <screen role='root'><userinput>cat > /etc/profile.d/extrapaths.sh << "EOF" -
archive/kde/core/pre-install-config.xml
52 52 </itemizedlist> 53 53 54 54 <para>The instructions for making these changes permanent are in 55 <xref linkend= 'kde-core-config'/>.</para>55 <xref linkend="kde-core-config"/>.</para> 56 56 57 57 <para>There are two other environment variables that need to be set to build 58 58 <application>Trinity/KDE3</application>. These are needed for all the -
archive/qt4.xml
413 413 <tip><para>The PATH, MANPATH, and PKG_CONFIG_PATH can be updated in 414 414 the extrapaths.sh (or other script) in the /etc/profile.d directory 415 415 if you set up the startup files as recommended in 416 <xref linkend= 'postlfs-config-profile'/>.</para></tip>416 <xref linkend="postlfs-config-profile"/>.</para></tip> 417 417 418 418 <para>As with most libraries, there is no explicit configuration to do. 419 419 After updating <filename>/etc/ld.so.conf</filename> as explained above, -
archive/udev.xml
31 31 <title>Introduction to Udev</title> 32 32 33 33 <note><para>If you installed LFS from SVN-20120719, LFS-7.2, or later, 34 use <xref linkend= 'udev-extras'/> instead of this page.</para></note>34 use <xref linkend="udev-extras"/> instead of this page.</para></note> 35 35 36 36 <para><application>Udev</application> was indeed installed in LFS and there 37 37 is no reason to reinstall it unless you are going to install a package such -
networking/textweb/lynx.xml
66 66 <xref linkend="zip"/>, 67 67 <xref linkend="unzip"/>, 68 68 an <xref linkend="server-mail"/> (that provides a <command>sendmail</command> command), and 69 <xref linkend= 'sharutils'/> (for a <command>uudecode</command> program)69 <xref linkend="sharutils"/> (for a <command>uudecode</command> program) 70 70 </para> 71 71 72 72 <!-- Attempt to utilize S-Lang (- -with-screen=slang) leads to a build failure -->