website diff en/doc/handbook/packages.html @ rev 117
en: Typos, spelling, wording, etc.
author | Mike D. Smith <MikeDSmith25@gmail.com> |
---|---|
date | Sat Jul 19 16:23:18 2008 +0000 (2008-07-19) |
parents | f7dbfd69ab3a |
children | 658f2885e2f2 |
line diff
1.1 --- a/en/doc/handbook/packages.html Wed Jun 25 18:45:59 2008 +0000 1.2 +++ b/en/doc/handbook/packages.html Sat Jul 19 16:23:18 2008 +0000 1.3 @@ -6,7 +6,7 @@ 1.4 <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" /> 1.5 <meta name="description" content="slitaz packages tazpkg install new applications upgrade list extract" /> 1.6 <meta name="expires" content="never" /> 1.7 - <meta name="modified" content="2008-02-26 18:30:00" /> 1.8 + <meta name="modified" content="2008-07-18 05:30:00" /> 1.9 <meta name="publisher" content="www.slitaz.org" /> 1.10 <meta name="author" content="Christophe Lincoln"/> 1.11 <link rel="shortcut icon" href="favicon.ico" /> 1.12 @@ -82,7 +82,7 @@ 1.13 </pre> 1.14 <p> 1.15 To get a single list of all available packages on the mirror you can use 1.16 -the command <code>list-mirror</code>, you can then examine the list in your favorite editor 1.17 +the command <code>list-mirror</code>. You can then examine the list in your favorite editor 1.18 or use the Web site interface. 1.19 </p> 1.20 1.21 @@ -122,10 +122,10 @@ 1.22 <p> 1.23 All SliTaz packages are built with a tool named Tazwok and a receipt found 1.24 in the wok. The receipt provides all the necessary information to build a suitable 1.25 -package for Tazpkg, variables to give us the package name, source tarball format, 1.26 -download URL, etc. With a receipt then the <code>compile_rules</code> function has got all 1.27 -the necessary commands to configure, make and install the package in a specific directory. 1.28 -After the compilation, Tazwok will execute the function <code>genpkg_rules</code> 1.29 +package for Tazpkg including variables to give us the package name, source tarball format, 1.30 +download URL, etc. Given a receipt the <code>compile_rules</code> function has all of 1.31 +the necessary commands to configure, make, and install the package in a specific directory. 1.32 +After compilation, Tazwok will execute the function <code>genpkg_rules</code> 1.33 to pick up only the needed/wanted files and generate a pkg.tazpkg (cpio archive). 1.34 On SliTaz you will find all installed package receipts in the directory 1.35 <code>/var/lib/tazpkg/installed</code>, feel free to examine them or even use one as an 1.36 @@ -133,9 +133,9 @@ 1.37 </p> 1.38 <p> 1.39 Tazwok will search by default for a wok in <code>/home/slitaz/wok</code> and 1.40 -put generated packages in <code>/home/slitaz/packages</code>, these paths are 1.41 +put generated packages in <code>/home/slitaz/packages</code>. These paths are 1.42 set by a Tazwok configuration file which can be located in 1.43 -<code>/etc/tazwok.conf</code> or in the current directory, this is useful if you 1.44 +<code>/etc/tazwok.conf</code> or in the current directory, which is useful if you 1.45 want to work with multiple woks. Now, if the <code>slitaz-toolchain</code> is 1.46 installed, you can start to create and build a package which doesn't need many 1.47 dependencies. Small example: