SliTaz Repositories

     1.1 --- a/en/devel/forge.php	Sun Mar 11 22:54:13 2012 +0100
     1.2 +++ b/en/devel/forge.php	Mon Mar 12 00:20:18 2012 +0100
     1.3 @@ -44,7 +44,7 @@
     1.4  	<li><a href="#repos">Mercurial repositories.</a></li>
     1.5  	<li><a href="#gui">GUI in GTK and CGI/web</a></li>
     1.6  	<li><a href="#iconv">Implementation of iconv().</a></li>
     1.7 -	<li><a href="#pkgs">Tazpkg packages.</a></li>
     1.8 +	<li><a href="#pkgs">Building SliTaz packages.</a></li>
     1.9  	<li><a href="#website">Website Management.</a></li>
    1.10  </ul>
    1.11  
    1.12 @@ -212,47 +212,52 @@
    1.13  <a name="iconv"></a>
    1.14  <h2>Implementation of iconv()</h2>
    1.15  <p>
    1.16 -SliTaz uses iconv() provided by GNU glibc - any packages that offer 
    1.17 -<code>libiconv</code> must use the library contained in <code>glibc-locale</code>. 
    1.18 -There is therefore no longer a libiconv package (1.2 MB) in SliTaz.
    1.19 +	SliTaz uses iconv() provided by GNU glibc - any packages that offer 
    1.20 +	<code>libiconv</code> must use the library contained in <code>glibc-locale</code>. 
    1.21 +	There is therefore no longer a libiconv package (1.2 MB) in SliTaz.
    1.22  </p>
    1.23  
    1.24  <a name="pkgs"></a>
    1.25 -<h2>Tazpkg Packages</h2>
    1.26 +<h2>Building SliTaz packages</h2>
    1.27  <p>
    1.28 -The tazpkg packages in SliTaz are automatically created via Tazwok and a 
    1.29 -receipt in the wok. The Cookbook describes the 
    1.30 -<a href="http://doc.slitaz.org/en:cookbook:wok">use of tools</a> 
    1.31 -and the format of <a href="http://doc.slitaz.org/en:cookbook:receipt">receipts</a>.
    1.32 -These are required reading before we begin.
    1.33 +	Building official is done with the Cookutils suite. The package is installed
    1.34 +	on each SliTaz system as well as the documentation about using cook and
    1.35 +	<a href="http://hg.slitaz.org/cookutils/raw-file/tip/doc/cookutils.en.html">creating SliTaz Packages</a> suitable fot TazPKG packages manager.
    1.36  </p>
    1.37  <p>
    1.38 -In terms of choice of package, the idea is to offer a package by task or 
    1.39 -functionality, ie. the lightest application in the field and not duplicated. 
    1.40 -Note that the current packages are not immutable, if you find an alternative 
    1.41 -that is lighter, with more features or more <em>sexy</em> for a few extra KB, 
    1.42 -you can suggest it on the Mailing List. Particular attention is given to 
    1.43 -packages for the LiveCD, these should be stripped, removing unnecesary 
    1.44 -dependencies and compiler options. In general candidate packages for the core 
    1.45 -LiveCD are discussed on the Mailing List.
    1.46 +	The tazpkg packages in SliTaz are automatically created via the
    1.47 +	<a href="http://cook.slitaz.org/">Cooker</a> from Cookutils package
    1.48 +	and a receipt in the wok. The Cookbook describes the format of 
    1.49 +	<a href="http://doc.slitaz.org/en:cookbook:receipt">receipts</a>.
    1.50 +	Cook and receipt documentation are required reading before we begin.
    1.51  </p>
    1.52  <p>
    1.53 -Before you begin to compile and create packages for SliTaz, be sure that the 
    1.54 -work doesn't already exist in the 
    1.55 -<a href="http://download.tuxfamily.org/slitaz/packages/undigest/">undigest</a> 
    1.56 -wok provided by the primary SliTaz mirror. Don't forget that the members 
    1.57 -of the list are there to help you and that the documentation of the 
    1.58 -<a href="http://doc.slitaz.org/en:cookbook:wok">wok and tools</a> 
    1.59 -exists to help you get started.
    1.60 +	In terms of choice of package, the idea is to offer a package by task or 
    1.61 +	functionality, ie. the lightest application in the field and not duplicated. 
    1.62 +	Note that the current packages are not immutable, if you find an alternative 
    1.63 +	that is lighter, with more features or more <em>sexy</em> for a few extra KB, 
    1.64 +	you can suggest it on the Mailing List. Particular attention is given to 
    1.65 +	packages for the LiveCD, these should be stripped, removing unnecesary 
    1.66 +	dependencies and compiler options. In general candidate packages for the core 
    1.67 +	LiveCD are discussed on the Mailing List.
    1.68 +</p>
    1.69 +<p>
    1.70 +	Before you begin to compile and create packages for SliTaz, be sure that the 
    1.71 +	work doesn't already exist in the 
    1.72 +	<a href="http://download.tuxfamily.org/slitaz/packages/undigest/">undigest</a> 
    1.73 +	wok provided by the primary SliTaz mirror. Don't forget that the members 
    1.74 +	of the list are there to help you and that the documentation of the 
    1.75 +	<a href="http://doc.slitaz.org/en:cookbook:wok">wok and tools</a> 
    1.76 +	exists to help you get started.
    1.77  </p>
    1.78  
    1.79  <a name="pkgs-naming"></a>
    1.80  <h3>Naming of packages</h3>
    1.81  <p>
    1.82 -In most cases the package name is the same as the source, except for
    1.83 -Python, Perl, PHP, Ruby and Lua modules. For example, the package
    1.84 -providing a Kid template system written in Python and XML is named:
    1.85 -<code>python-kid</code>.
    1.86 +	In most cases the package name is the same as the source, except for
    1.87 +	Python, Perl, PHP, Ruby and Lua modules. For example, the package
    1.88 +	providing a Kid template system written in Python and XML is named:
    1.89 +	<code>python-kid</code>.
    1.90  </p>
    1.91  
    1.92  <a name="website"></a>
    1.93 @@ -268,25 +273,25 @@
    1.94  
    1.95  <h3>xHTML coding style</h3>
    1.96  <p>
    1.97 -The pages and different <em>books</em> are coded in xHTML 1.0
    1.98 -transitional. The title of level 1 is used only once (at the top), 
    1.99 -level 2 is the title of the document and levels 3 and 4 are then used for
   1.100 -the subtitles. If a list is used instead using smart anchors;
   1.101 -then that starts at the top, just after the title of level 2.
   1.102 -Paragraphs are contained in the tags <code>&lt;p&gt;&lt;/p&gt;</code>. 
   1.103 -For indentation, we use tabs - the reason being semantics and to take 
   1.104 -up less space in terms of octets (bytes). To put code, like the name of
   1.105 -a command inside a paragraph: <code>&lt;code&gt;</code> is the preferred 
   1.106 -method. To view commands or to utilize a terminal, the web pages use
   1.107 -<code>&lt;pre&gt;</code> to display the formatted text. Example:
   1.108 +	The pages and different <em>books</em> are coded in xHTML 1.0
   1.109 +	transitional. The title of level 1 is used only once (at the top), 
   1.110 +	level 2 is the title of the document and levels 3 and 4 are then used for
   1.111 +	the subtitles. If a list is used instead using smart anchors;
   1.112 +	then that starts at the top, just after the title of level 2.
   1.113 +	Paragraphs are contained in the tags <code>&lt;p&gt;&lt;/p&gt;</code>. 
   1.114 +	For indentation, we use tabs - the reason being semantics and to take 
   1.115 +	up less space in terms of octets (bytes). To put code, like the name of
   1.116 +	a command inside a paragraph: <code>&lt;code&gt;</code> is the preferred 
   1.117 +	method. To view commands or to utilize a terminal, the web pages use
   1.118 +	<code>&lt;pre&gt;</code> to display the formatted text. Example:
   1.119  </p>
   1.120  <pre>
   1.121   $ command
   1.122  </pre>
   1.123  <p>
   1.124 -To view text that can be copied and pasted, such as scripts,
   1.125 -bits of code, sample configuration files, etc - we also use
   1.126 -<code>&lt;pre&gt;</code>, but with a CSS class named "script". Example:
   1.127 +	To view text that can be copied and pasted, such as scripts,
   1.128 +	bits of code, sample configuration files, etc - we also use
   1.129 +	<code>&lt;pre&gt;</code>, but with a CSS class named "script". Example:
   1.130  </p>
   1.131  <pre class="script">
   1.132  &lt;pre class="script"&gt;
   1.133 @@ -296,19 +301,19 @@
   1.134  &lt;/pre&gt;
   1.135  </pre>
   1.136  <p>
   1.137 -The <em>emphasized</em> words put themselves in the tag <code>&lt;em&gt;</code> 
   1.138 -and internal links are relative. Remember to check the validity
   1.139 -of the code via the online <em>validator</em> of the W3C.
   1.140 +	The <em>emphasized</em> words put themselves in the tag <code>&lt;em&gt;</code> 
   1.141 +	and internal links are relative. Remember to check the validity
   1.142 +	of the code via the online <em>validator</em> of the W3C.
   1.143  </p>
   1.144  
   1.145  <a name="diff"></a>
   1.146  <h2>Diff and patch</h2>
   1.147  <p>
   1.148 -The utilities <code>diff</code> and <code>patch</code> are command-line tools 
   1.149 -for creating and implementing a file containing differences between two files. 
   1.150 -This technique is often used for collaboration and the changes made to the 
   1.151 -original file can be clearly extracted. To create a <code>diff</code> file 
   1.152 -readable by humans in a simple text editor, you must supply the <code>-u</code> option:
   1.153 +	The utilities <code>diff</code> and <code>patch</code> are command-line tools 
   1.154 +	for creating and implementing a file containing differences between two files. 
   1.155 +	This technique is often used for collaboration and the changes made to the 
   1.156 +	original file can be clearly extracted. To create a <code>diff</code> file 
   1.157 +	readable by humans in a simple text editor, you must supply the <code>-u</code> option:
   1.158  </p>
   1.159  <pre>
   1.160   $ diff -u file.orig file.new &gt; file.diff