24 |
</copyright> |
</copyright> |
25 |
<revhistory> |
<revhistory> |
26 |
<!-- comment this first revision out when releasing a real version --> |
<!-- comment this first revision out when releasing a real version --> |
27 |
|
<!-- |
28 |
<revision> |
<revision> |
29 |
<revnumber>1.0pre1 CVS $Id$</revnumber> |
<revnumber>CVS version $Id$</revnumber> |
30 |
<date>$Date$</date> |
<date></date> |
31 |
<revremark>Under development.</revremark> |
<revremark>Under development.</revremark> |
32 |
</revision> |
</revision> |
33 |
|
--> |
34 |
|
<revision> |
35 |
|
<revnumber>1.0pre2</revnumber> |
36 |
|
<date>29-Aug-2003</date> |
37 |
|
<revremark> |
38 |
|
Corresponds to Thuban development release 0.8.1. |
39 |
|
New: chapter on extensions. |
40 |
|
</revremark> |
41 |
|
</revision> |
42 |
<revision> |
<revision> |
43 |
<revnumber>1.0pre1</revnumber> |
<revnumber>1.0pre1</revnumber> |
44 |
<date>08-Aug-2003</date> |
<date>08-Aug-2003</date> |
45 |
<revremark>Corresponds to Thuban development release 0.8.1</revremark> |
<revremark>Corresponds to Thuban development release 0.8.1.</revremark> |
46 |
</revision> |
</revision> |
47 |
</revhistory> |
</revhistory> |
48 |
|
|
95 |
full installation packages for Debian, Windows and RPM-based systems |
full installation packages for Debian, Windows and RPM-based systems |
96 |
(Mandrake, RedHat, SuSE, etc). |
(Mandrake, RedHat, SuSE, etc). |
97 |
</para> |
</para> |
98 |
|
<section><title>RPM-based GNU/Linux Systems</title> |
99 |
|
<section><title>Installing Binary Packages</title> |
100 |
|
<para> |
101 |
|
The most wide-spread RPM-based GNU/Linux Systems are RedHat, |
102 |
|
Mandrake and SuSE. The documentation of these distributions |
103 |
|
should contain information about how to install third-party |
104 |
|
RPM packages. Nonetheless, a short summary is provided here. |
105 |
|
</para> |
106 |
|
<para> |
107 |
|
RPM packages can be installed applying several tools. |
108 |
|
The most basic one is the command line program "rpm". |
109 |
|
The hardware architecture is identified in the name |
110 |
|
of RPM packages, eg. 'i386' for most Intel/AMD architectures. |
111 |
|
If you have a different hardware architecture, where no |
112 |
|
binary RPM packages are provided, you must rebuild binary |
113 |
|
packages from the RPM source packages first (see below). |
114 |
|
Typical rpm commands look like: |
115 |
|
|
116 |
|
<programlisting> |
117 |
|
rpm --install Thuban-0.9.0-1.i386.rpm |
118 |
|
</programlisting> |
119 |
|
|
120 |
|
Depending on what you already have installed on your |
121 |
|
system, you are informed that some packages are |
122 |
|
required, but not installed. You need to install them |
123 |
|
first. Either they are provided by your GNU/Linux distributor |
124 |
|
or available somewhere on the Internet. |
125 |
|
The more essential and special ones are provided together |
126 |
|
with the Thuban package. |
127 |
|
</para> |
128 |
|
|
129 |
|
<para> |
130 |
|
For rpm exist some graphical user interfaces, notably |
131 |
|
kpackage, GnoRPM and xrpm. |
132 |
|
</para> |
133 |
|
|
134 |
|
<para> |
135 |
|
Make yourself familiar with one of the tools and apply it |
136 |
|
to install the packages. |
137 |
|
Note, that you need to be administrator (root) for the system |
138 |
|
to do that. |
139 |
|
</para> |
140 |
|
</section> |
141 |
|
<section><title>Build Binaries from Source Packages</title> |
142 |
|
<para> |
143 |
|
This section describes howto build RPM install-packages |
144 |
|
from RPM source-packages. |
145 |
|
This adapts and optimizes an install-package specifically |
146 |
|
to your system. |
147 |
|
This is especially helpful to resolve version conflicts of |
148 |
|
dependent packages. Furthermore, install-packages for other |
149 |
|
platforms (e.g. PowerPC) can be created. |
150 |
|
</para> |
151 |
|
|
152 |
|
<para> |
153 |
|
Note: rpm must be at least version 4. Execute |
154 |
|
<literal>rpm --version</literal> to find out about the version. |
155 |
|
</para> |
156 |
|
|
157 |
|
<para> |
158 |
|
You need to do the following preparations to be able to |
159 |
|
build the packages as a regular user. You should now |
160 |
|
perform the package buling as root since this |
161 |
|
might cause damage to your system. |
162 |
|
<itemizedlist> |
163 |
|
<listitem> |
164 |
|
<para> |
165 |
|
Create RPM directory structure: |
166 |
|
Choose a directory (e.g. $HOME/myrpm) and create the |
167 |
|
subdirectories BUILD, RPM, SOURCES, SPECS and SRPMS. |
168 |
|
A possible command sequence for this is: |
169 |
|
<programlisting> |
170 |
|
mkdir $HOME/freegisrpm |
171 |
|
cd $HOME/freegisrpm |
172 |
|
mkdir BUILD RPMS SOURCES SPECS SRPMS |
173 |
|
</programlisting> |
174 |
|
</para> |
175 |
|
</listitem> |
176 |
|
<listitem> |
177 |
|
<para> |
178 |
|
Set environment variable RPM_DIR: |
179 |
|
<programlisting> |
180 |
|
export RPM_DIR=$HOME/freegisrpm |
181 |
|
</programlisting> |
182 |
|
</para> |
183 |
|
</listitem> |
184 |
|
<listitem> |
185 |
|
<para> |
186 |
|
Create $HOME/.rpmmacros: |
187 |
|
This file sets general preferences and some |
188 |
|
specific settings for signing packages. |
189 |
|
If you don't have a GnuPG-key, you can skip |
190 |
|
the signature settings i.e. drop the last 4 lines. |
191 |
|
A signature becomes important when you want to |
192 |
|
give away packages to third parties. |
193 |
|
<programlisting> |
194 |
|
<![CDATA[ |
195 |
|
%packager Name Lastname <[email protected]> |
196 |
|
|
197 |
|
%_topdir /home/mylogin/myrpm |
198 |
|
|
199 |
|
%_signature gpg |
200 |
|
%_gpg_name Name Lastname |
201 |
|
%_pgp_path ~/.gnupg |
202 |
|
%_pgpbin /usr/bin/gpg |
203 |
|
]]> |
204 |
|
</programlisting> |
205 |
|
</para> |
206 |
|
</listitem> |
207 |
|
</itemizedlist> |
208 |
|
|
209 |
|
Now you can install any RPM source-package. |
210 |
|
It's components are installed into the corresponding |
211 |
|
subdirectories of your rpm-directory. |
212 |
|
Essentially these are the sources (into directory SOURCES) |
213 |
|
and the so-called spec-file which contains all build |
214 |
|
instructions. The spec-file will go into the SPEC directory. |
215 |
|
Example: |
216 |
|
<literal>rpm --install Thuban-0.9.0-1.src.rpm</literal> |
217 |
|
</para> |
218 |
|
|
219 |
|
<para> |
220 |
|
Create install-package: |
221 |
|
Go to the directory with the spec-files and rebuild the |
222 |
|
package: |
223 |
|
<programlisting> |
224 |
|
cd $HOME/mypm/SPECS |
225 |
|
rpm -bb thuban.spec |
226 |
|
</programlisting> |
227 |
|
Next, you will find the newly created package in |
228 |
|
$HOME/myrpm/RPMS/i386. |
229 |
|
If you build the package for another architecture than |
230 |
|
i386, then the name of the directory has a corresponding name. |
231 |
|
</para> |
232 |
|
<para> |
233 |
|
For documentation of RPM, either type |
234 |
|
<literal>man rpm</literal> or <literal>rpm --help</literal>. |
235 |
|
This will provide you with information on the various command |
236 |
|
line options of RPM. |
237 |
|
For more information see the |
238 |
|
<ulink url="http://www.rpm.org/">homepage of RPM</ulink>. |
239 |
|
</para> |
240 |
|
</section> |
241 |
|
</section> |
242 |
</section> |
</section> |
243 |
|
|
244 |
<section><title>The Main Window</title> |
<section><title>The Main Window</title> |
1396 |
to this file to keep the actual code of extensions separate. |
to this file to keep the actual code of extensions separate. |
1397 |
</para> |
</para> |
1398 |
<para> |
<para> |
1399 |
The modules to import must either be found though the environment |
The modules to import must either be found through the environment |
1400 |
variable PYTHONPATH or directly be placed into the .thuban-directory. |
variable PYTHONPATH or directly be placed into the .thuban-directory. |
1401 |
</para> |
</para> |
1402 |
<para> |
<para> |