Changeset 6ad6bac
- Timestamp:
- 01/06/2023 12:41:33 AM (16 months ago)
- Branches:
- 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/llvm18, xry111/xf86-video-removal
- Children:
- 6a6d01e
- Parents:
- 06c23e6
- Location:
- introduction
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/important/beyond.xml
r06c23e6 r6ad6bac 165 165 </listitem> 166 166 <listitem> 167 <para>Gentoo - the mirrors for ebuilds and patches seem to be well-hidden, 168 and they change frequently. Also, if you have found a mirror, you need to 169 know which directory the application has been assigned to. The ebuilds 170 themselves can be found at <ulink url="https://packages.gentoo.org/"/> - 171 use the search field. If there are any patches, a mirror will have them 172 in the <filename class="directory">files/</filename> directory. Depending 173 on your browser, or the mirror, you might need to download the ebuild to 174 be able to read it. Treat the ebuild as a sort of pseudo-code / shell 175 combination - look in particular for <command>sed</command> commands and 176 patches, or hazard a guess at the meanings of the functions such as 177 <command>dodoc</command>.</para> 167 <para>Gentoo - First use a search engine to find an ebuild which looks as 168 if it will fix the problem, or search at <ulink 169 url="https://packages.gentoo.org/"/> - use the search field. Note where the 170 package lives in the portage hierarchy, e.g. 171 <filename>app-something/</filename>. In general you can treat the ebuild as 172 a sort of pseudo-code / shell combination with some functions you can 173 hazard a guess at, such as <command>dodoc</command>. If the fix is just a 174 <command>sed</command>, try it. However, in most cases the fix will use a 175 patch. To find the patch, use a gentoo-portage mirror: Two links to mirrors 176 in the U.S.A. which seem to usually be up to date are 177 <ulink url="https://mirror.rackspace.com/gentoo-portage/"/> and 178 <ulink url="https://mirror.steadfast.net/gentoo-portage/"/>. Navigate down 179 the tree to the package, then to the <filename>files/</filename> directory 180 to look for the patch. Sometimes a portage mirror has not yet been updated, 181 particularly for a recent new patch. In a few cases, gentoo batch the 182 patches into a tarball and the ebuild will have a link in the form 183 https://dev.gentoo.org/~${PATCH_DEV}/distfiles/${P}-patches-${PATCH_VER}.tar.xz 184 : here, look for PATCH_DEV and PATCH_VER in the build and format the full 185 URL in your browser or for wget : remember the '~' before the developer's 186 ID and note that trying to search the earlier levels of the URL in a 187 browser may drop you at www.gentoo.org or return 403 (forbidden). 188 </para> 178 189 </listitem> 179 190 <listitem> -
introduction/welcome/changelog.xml
r06c23e6 r6ad6bac 40 40 --> 41 41 <listitem> 42 <para>January 5th, 2023</para> 43 <itemizedlist> 44 <listitem> 45 <para>[ken] - Expand the gentoo details in 'Going Beyond BLFS'. Fixes 46 <ulink url="&blfs-ticket-root;17004">#17004</ulink>.</para> 47 </listitem> 48 </itemizedlist> 49 </listitem> 50 51 <listitem> 42 52 <para>January 4th, 2023</para> 43 53 <itemizedlist>
Note:
See TracChangeset
for help on using the changeset viewer.