Changeset 4d3e5f1 for introduction/important/building-notes.xml
- Timestamp:
- 09/25/2009 10:52:41 AM (15 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 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:
- de2551f
- Parents:
- 9cc3fde
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/important/building-notes.xml
r9cc3fde r4d3e5f1 81 81 <para>Finally, you sometimes need to be able to unpack patches which are 82 82 generally not in <filename class='extension'>.tar</filename> format. The 83 best way to do this is to copy the patch file to parent of the 'build'83 best way to do this is to copy the patch file to the parent of the 'build' 84 84 directory and then run one of the following commands depending on whether 85 85 the file is a <filename class='extension'>.gz</filename> or <filename
Note:
See TracChangeset
for help on using the changeset viewer.