website view en/devel/index.html @ rev 39
Add LightTPD to Handbook (en) & typos
| author | Paul Issott <paul@slitaz.org> |
|---|---|
| date | Wed May 04 21:16:27 2011 +0000 (2011-05-04) |
| parents | 7194d2ac8f55 |
| children | 6eff36f0e2a3 |
line source
1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
4 <head>
5 <title>SliTaz - Developers corner</title>
6 <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" />
7 <meta name="description" content="SliTaz GNU/Linux project information overview" />
8 <meta name="keywords" lang="en" content="about slitaz, gnu, linux, mini distro, livecd" />
9 <meta name="robots" content="index, follow, all" />
10 <meta name="revisit-after" content="7 days" />
11 <meta name="expires" content="never" />
12 <meta name="modified" content="2008-04-12 23:30:00" />
13 <meta name="author" content="Christophe Lincoln"/>
14 <meta name="publisher" content="www.slitaz.org" />
15 <link rel="shortcut icon" href="../../favicon.ico" />
16 <link rel="stylesheet" type="text/css" href="../../slitaz.css" />
17 </head>
18 <body bgcolor="#ffffff">
19 <!-- Header -->
20 <div id="header">
21 <a name="top"></a>
22 <!-- Access -->
23 <div id="access">
24 <a href="#content" title="Page content">Content</a> |
25 <a href="../../devel/" title="A propos de SliTaz en français">Français</a>
26 </div>
27 <a href="http://www.slitaz.org/en/"><img id="logo"
28 src="../../pics/website/logo.png" title="www.slitaz.org/en" alt="www.slitaz.org"
29 style="border: 0px solid ; width: 200px; height: 74px;" /></a>
30 <p id="titre">#!/GNU/Linux</p>
31 </div>
32 <div id="nav">
33 <div id="nav_top"></div>
34 <ul>
35 <li><a href="../about/" title="Informations about the SliTaz project">About the project</a></li>
36 <li><a href="../get/" title="Download - LiveCD ISO">Get SliTaz</a></li>
37 <li><a href="../doc/" title="LiveCD usage and howto">Documentation</a></li>
38 <li><a href="../packages/" title="Packaged software">Packages</a></li>
39 <li><a href="../mailing-list.html" title="Support, contact and collaboration">Mailing List</a></li>
40 <li><a href="../devel/" title="Developer corner">Developement</a></li>
41 <li><a href="../artwork/" title="Artwork, colors and images">Artwork</a></li>
42 <li><a href="../search.html" title="Search engine">Search</a></li>
43 <li><a href="../sitemap.html" title="Web site overview">Sitemap</a></li>
44 <li><a href="http://forum.slitaz.org/#idx2" title="English support forum">Forum</a></li>
45 </ul>
46 <div id="nav_bottom">
47 <div id="nav_bottom_img"></div>
48 </div>
49 </div>
51 <!-- Content top. -->
52 <div id="content_top">
53 <div class="top_left"></div>
54 <div class="top_right"></div>
55 </div>
57 <!-- Content -->
58 <div id="content">
59 <a name="content"></a>
61 <h1><font color="#3e1220">Developement</font></h1>
62 <h2><font color="#df8f06">SliTaz Developers corner</font></h2>
64 <ul>
65 <li><a href="#repos">Mercurial repositories.</a></li>
66 <li><a href="#pkgs">Tazpkg packages.</a></li>
67 <li><a href="#website">Website Management.</a></li>
68 <li><a href="../mailing-list.html">Mailing List.</a></li>
69 <li><a href="../doc/cookbook/wok-tools.html">Wok & Tools.</a></li>
70 <li>Hg repositories: <a href="http://hg.slitaz.org" >hg.slitaz.org</a></li>
71 <li>Scratchpad: <a href="http://wiki.slitaz.org/">wiki.slitaz.org</a></li>
72 </ul>
74 <p>
75 SliTaz is an open source and community driven distribution. Everyone is welcome
76 to join and contribute, from users, to hackers and developers there is always
77 something to do, ie. Proofreading or writing documentation, sending bugs or
78 patches to the Mailing list, gaining access to the wok and pushing some new
79 packages or simply to help others on the Mailing list or forum. SliTaz has got
80 Mercurial repositories hosted on a SliTaz system, developers can ask for a new
81 repo if needed and contributors have write access to correct typos, scripts, etc.
82 </p>
84 <p>
85 SliTaz is a tiny community and listens to it's users. There are several
86 developers who are active on the <a href="http://forum.slitaz.org/">forum</a>
87 and the <a href="../mailing-list.html">Mailing List</a>.
88 </p>
90 <a name="repos"></a>
91 <h3>Mercurial repositories</h3>
92 <p>
93 SliTaz Mercurial or Hg repos can be browsed or cloned by anyone using the URL:
94 <a href="http://hg.slitaz.org/">http://hg.slitaz.org/</a>. People with write
95 access can directly use <code>repos.slitaz.org</code> which needs authentication.
96 Mercurial uses Python and is installable with:
97 <code>tazpkg get-install mercurial</code>
98 </p>
99 <h4>~/.hgrc</h4>
100 <p>
101 Before you push your first commit onto the server, be sure you have a correct
102 Hg configuration file with your name and email address and remember to check
103 that you are not root. Personal ~/.hgrc file example:
104 </p>
105 <pre class="script">
106 [ui]
107 username = Name FirstName <you@example.org>
108 </pre>
109 <h4>Clone, modify, commit and push</h4>
110 <p>
111 Clone a repo, example for slitaz-doc:
112 </p>
113 <pre>
114 $ hg clone http://repos.slitaz.org/slitaz-doc
115 </pre>
116 <p>
117 Change directory to slitaz-doc, note you must be in the repository to be able
118 to use 'hg' commands. To check all logs or just the last log:
119 </p>
120 <pre>
121 $ hg log
122 $ hg head
123 </pre>
124 <p>
125 Modify one or more files and commit:
126 </p>
127 <pre>
128 $ hg status
129 $ hg commit -m "Log message..."
130 $ hg log
131 </pre>
132 <p>
133 Note that you can use the command <code>rollback</code> to roll back to the last
134 transaction. Before pushing changes to the server it is safe to pull once:
135 </p>
136 <pre>
137 $ hg pull
138 $ hg push
139 </pre>
140 <p>
141 Done, your changes, code or corrections are now on the server.
142 </p>
144 <a name="pkgs"></a>
145 <h3>Tazpkg Packages</h3>
146 <p>
147 The packages tazpkg in SliTaz are automatically created via Tazwok and a
148 receipt in the wok, the Cookbook describes the
149 <a href="../doc/cookbook/wok-tools.html">use of tools</a>
150 and the format <a href="../doc/cookbook/receipts.html">receipts</a>,
151 These are required reading before we begin.
152 </p>
153 <p>
154 In terms of choice of package, the idea is to offer a package by task or
155 functionality, ie. the lightest application in the field and not duplicated.
156 Note that the current packages are not immutable, if you find an alternative
157 that is lighter, with more features or more <em>sexy</em> for a few extra KB,
158 you can suggest it on the Mailing List. Particular attention is given to
159 packages for the LiveCD; these should be stripped, removing unnecesary
160 dependancies and compiler options. In general candidate packages for the core
161 LiveCD are discussed on the Mailing List.
162 </p>
163 <p>
164 Before you begin to compile and create packages for SliTaz, be sure that the
165 work doesn't already exist in the wok indigest provided by the primary SliTaz
166 mirror. Don't forget that the members of the list are there to help you
167 and that the documentation of the
168 <a href="../doc/cookbook/wok-tools.html">wok and tools</a>
169 exists to help you get started.
170 </p>
172 <a name="website"></a>
173 <h3>Website Management and Books</h3>
174 <p>
175 The management of the website and books (Handbook & Cookbook) is made via
176 a rsync module, Mercurial, diff and patch utilities and the Mailing List.
177 Rsync is a tool for incremental backup; using an ultra-fast algorithm, It can
178 transfer or syncronize data both locally or over the network. The
179 <code>diff</code> utility is used to send the list of files containing only
180 the changes and <code>patch</code> to apply the changes to the original pages.
181 </p>
182 <p>
183 You can syncronize the site and books graphically using Grsync or via the
184 command line. To download the site for the first time or syncronize the pages
185 in the directory <code>/home/hacker/Public/slitaz/website</code>,
186 use the module <code>rsync://slitaz.org/website</code>:
187 </p>
188 <pre>
189 $ rsync -r -t -p -v \
190 --progress --delete \
191 rsync://slitaz.org/website /home/hacker/Public/slitaz/website
192 </pre>
193 <h4>Diff and patch</h4>
194 <p>
195 The utilities <code>diff</code> and <code>patch</code> are command-line tools
196 for creating and implementing the differences between two files. This technique
197 is often used for collaboration and the changes made to the original file can
198 be clearly extracted. To create a <code>diff</code> file readable by humans in
199 a simple text editor, you must supply the <code>-u</code> option:
200 </p>
201 <pre>
202 $ diff -u file.orig file.new > file.diff
203 </pre>
204 <p>
205 To apply a patch:
206 </p>
207 <pre>
208 $ patch file.orig file.diff
209 </pre>
211 <!-- End of content with round corner -->
212 </div>
213 <div id="content_bottom">
214 <div class="bottom_left"></div>
215 <div class="bottom_right"></div>
216 </div>
218 <!-- Start of footer and copy notice -->
219 <div id="copy">
220 <p>
221 Last modification : 2008-04-12 23:30:00 -
222 <a href="#top">Top of the page</a>
223 </p>
224 <p>
225 Copyright © 2008 <a href="http://www.slitaz.org/">SliTaz</a> -
226 <a href="http://www.gnu.org/licenses/gpl.html">GNU General Public License</a>
227 </p>
228 <!-- End of copy -->
229 </div>
231 <!-- Bottom and logo's -->
232 <div id="bottom">
233 <p>
234 <a href="http://validator.w3.org/check?uri=referer"><img
235 src="../../pics/website/xhtml10.png" alt="Valid XHTML 1.0"
236 title="Code validé XHTML 1.0"
237 style="width: 80px; height: 15px;" /></a>
238 </p>
239 </div>
241 </body>
242 </html>