Changeset c40a9d0 for introduction/important
- Timestamp:
- 08/17/2005 02:18:47 AM (19 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.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:
- 4096f25
- Parents:
- 79630dd
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/important/unpacking.xml
r79630dd rc40a9d0 26 26 instructions.</para> 27 27 28 <para>While you can keep the source files anywhere you like, we 29 assume that you have unpacked them and unzipped any required patches 30 into <filename>/usr/src</filename>.</para> 28 <para>While you can keep the source files anywhere you like, we assume that 29 you have unpacked the package and changed into the directory created by the 30 unpacking process (the 'build' directory). We also assume you have 31 uncompressed any required patches and they are in the directory immediately 32 above the 'build' directory.</para> 31 33 32 34 <para>We can not emphasize strongly enough that you should start from a … … 78 80 <para>Finally, you sometimes need to be able to unpack patches which are 79 81 generally not in <filename class='extension'>.tar</filename> format. The 80 best way to do this is to copy the patch file to 81 <filename class='directory'>/usr/src</filename> and then run one of the 82 following commands depending on whether the file is a 83 <filename class='extension'>.gz</filename> or 84 <filename class='extension'>.bz2</filename> file:</para> 82 best way to do this is to copy the patch file to parent of the 'build' 83 directory and then run one of the following commands depending on whether 84 the file is a <filename class='extension'>.gz</filename> or <filename 85 class='extension'>.bz2</filename> file:</para> 85 86 86 87 <screen><userinput>gunzip -v patchname.gz
Note:
See TracChangeset
for help on using the changeset viewer.