Changeset 6ed5123 for introduction/important
- Timestamp:
- 07/09/2012 06:31:25 PM (12 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 12.2, 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, gimp3, 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/for-12.3, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/spidermonkey128, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 2f4014b
- Parents:
- a716dec
- Location:
- introduction/important
- Files:
-
- 1 added
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/important/beyond.xml
ra716dec r6ed5123 83 83 <itemizedlist> 84 84 <listitem> 85 <para>If you know the name of the package, then search Fre shMeatfor86 it at <ulink url="http://fre shmeat.net/"/>. Also search Google at85 <para>If you know the name of the package, then search Freecode for 86 it at <ulink url="http://freecode.com/"/>. Also search Google at 87 87 <ulink url="http://google.com/"/>. Sometimes a search for the 88 88 <filename class='extension'>rpm</filename> at … … 120 120 searching the LFS archives at 121 121 <ulink url="http://www.&lfs-domainname;/search.html"/> for the error or if 122 that fails, try searching Google. If everything else fails, 123 try the blfs-support mailing-list.</para> 122 that fails, try searching Google. Often, a distribution will have already 123 solved the problem (many of them use development versions of packages, so 124 they see the changes sooner than those of us who normally use stable released 125 versions). But be cautious - all builders tend to carry patches which are no 126 longer necessary, and to have fixes which are only required because of their 127 particular choices in how they build a package. You may have to search 128 deeply to find a fix for the package version you are trying to use, or even 129 to find the package (names are sometimes not what you might expect, e.g. 130 <application>ghostscript</application> often has a prefix or a suffix in its 131 name), but the following notes might help:</para> 132 <itemizedlist> 133 <listitem> 134 <para>Arch 135 <ulink url="http://www.archlinux.org/packages/"/> - enter the package name 136 in the 'Keywords' box, select the package name, select one of the 'SVN 137 Entries' fields, then select the <filename>PKGBUILD</filename> to see how 138 they build this package, or look at any patches.</para> 139 </listitem> 140 <listitem> 141 <para>Debian 142 <ulink url="ftp://ftp.uk.debian.org/debian/pool"/> (use your country's 143 version if there is one) - the source will be in .tar.gz tarballs (either 144 the original upstream <filename class='extension'>.orig</filename> source, 145 or else a <filename>dfsg</filename> containing those parts which comply 146 with debian's free software guidelines) accompanied by versioned .diff.gz 147 or .tar.gz additions. These additions often show how the package is built, 148 and may contain patches. In the .diff.gz versions, any patches create files 149 in <filename class="directory">debian/patches</filename>.</para> 150 </listitem> 151 <listitem> 152 <para>Fedora 153 <ulink url="http://pkgs.fedoraproject.org/gitweb/"/> - this site 154 is often overloaded since they moved to git-web, but when available it is 155 an easy way of looking at .spec files and patches. If unavailable, try 156 looking for a local mirror of ftp.fedora.com (the primary site is usually 157 unavailable when fedora gitweb is not responding) and download a source 158 rpm to see what they do.</para> 159 </listitem> 160 <listitem> 161 <para>Gentoo - the mirrors for ebuilds and patches seem to be well-hidden, 162 and they change frequently. Also, if you have found a mirror, you need to 163 know which directory the application has been assigned to. The ebuilds 164 themselves can be found at <ulink url="http://packages.gentoo.org/"/> - 165 use the search field. If there are any patches, a mirror will have them 166 in the <filename class="directory">files/</filename> directory. Depending 167 on your browser, or the mirror, you might need to download the ebuild to 168 be able to read it. Treat the ebuild as a sort of pseudo-code / shell 169 combination - look in particular for <command>sed</command> commands and 170 patches, or hazard a guess at the meanings of the functions such as 171 <command>dodoc</command>.</para> 172 </listitem> 173 <listitem> 174 <para>PLD 175 <ulink url="http://cvs.pld-linux.org/cgi-bin/cvsweb/packages/"/> - 176 another distro which uses rpms, cvsweb provides access to patches and the 177 spec files.</para> 178 </listitem> 179 <listitem> 180 <para>Slackware - the official package browser is currently broken. The 181 site at <ulink url="http://slackbuilds.org/"/> has current and previous 182 versions in their unofficial repository with links to homepages, downloads, 183 and some individual files, particularly the <filename>.SlackBuild</filename> 184 files.</para> 185 </listitem> 186 <listitem> 187 <para>Ubuntu <ulink url="ftp://ftp.ubuntu.com/ubuntu/pool/"/> - see the 188 debian notes above.</para> 189 </listitem> 190 </itemizedlist> 191 <para>If everything else fails, try the blfs-support mailing-list.</para> 124 192 </listitem> 125 193 </itemizedlist> … … 134 202 <ulink url="&downloads-project;/rpm2targz.tar.bz2"/> to convert the archives 135 203 into a simple <filename>tar.gz</filename> format.</para> 204 <para>You may also find an rpm2cpio script useful. The perl version in the 205 linux kernel archives at <ulink 206 url="http://lkml.indiana.edu/hypermail/linux/kernel/0210.2/att-0093/01-rpm2cpio"/> 207 works for most source rpms. The rpm2targz script will use an rpm2cpio script 208 or binary if one is on your path. Note that rpm2cpio will unpack a source 209 rpm in the current directory, giving a tarball, a spec file, and perhaps patches 210 or other files.</para> 136 211 </tip> 137 212 -
introduction/important/important.xml
ra716dec r6ed5123 27 27 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="patches.xml"/> 28 28 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="bootscripts.xml"/> 29 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="libraries.xml"/> 29 30 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="locale-issues.xml"/> 30 31 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="beyond.xml"/>
Note:
See TracChangeset
for help on using the changeset viewer.