source: archive/kde/kde-intro.xml@ 54bd123

11.1 lazarus qt5new trunk upgradedb xry111/intltool xry111/test-20220226
Last change on this file since 54bd123 was 45ab6c7, checked in by Xi Ruoyao <xry111@…>, 13 months ago

more SVN prop clean up

Remove "$LastChanged$" everywhere, and also some unused $Date$

  • Property mode set to 100644
File size: 2.9 KB
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE partintro PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "" [
4 <!ENTITY % general-entities SYSTEM "../general.ent">
5 %general-entities;
9 <title>Introduction to Trinity/KDE3</title>
11 <para>Trinity is a project that aims to keep the KDE 3.5 computing style
12 alive, as well as keeping the existing code base current. It is a
13 comprehensive desktop environment that builds on an <application>X Window
14 System</application> and <application>Qt</application> version 3 to provide a
15 window manager and many user tools, including a browser, word processor,
16 spreadsheet, presentation package, games, and numerous other utilities. It
17 provides extensive capabilities for customization.</para>
19 <para>The <application>Trinity/KDE3</application> instructions are divided into
20 three parts. The first part, the core packages, are needed for the rest of
21 <application>Trinity/KDE3</application> to work. The second part presents additional
22 packages which provide functionality in various areas (multimedia, graphics, etc.)
23 The third part provides resources for software and web developers.</para>
25 <para>There are two alternatives for installing
26 <application>Trinity/KDE3</application>. Option one, that is used by most of
27 the commercial distributions, is to install
28 <application>Trinity/KDE3</application> in the standard system prefix:
29 <filename class="directory">/usr</filename>. This option allows the use of
30 <application>Trinity/KDE3</application> without the need for any additional
31 configuration such as modification of various environment variables or
32 configuration files. Option two, recommended by the Trinity developers and
33 BLFS Editors is to install it in a unique prefix such as <filename
34 class="directory">/opt/trinity</filename> or <filename
35 class="directory">/opt/trinity-&trinity-version;</filename>. This option
36 allows for easy removal of the <application>Trinity/KDE3</application>
37 version or maintenance of multiple versions for testing.</para>
39 <para>The <application>Trinity/KDE3</application> pakages are undergoing
40 constant upgrades. With the 3.5.13 version, the core packages are
41 configured with <userinput>cmake</userinput> and the rest are built using the
42 traditional <userinput>configure</userinput> command.</para>
44 <tip>
45 <para>All the <application>Trinity/KDE3</application> packages that are
46 built with <userinput>configure</userinput> are comprised of various
47 components. The default is to install most of the components. If specific
48 components are to be eliminated, the way is to set the variable
49 <envar>DO_NOT_COMPILE</envar>. This comes in handy when there are problems
50 compiling a particular component.</para>
52<screen><userinput>DO_NOT_COMPILE="component1 component2" \
53 ./configure --prefix=$TRINITY_PREFIX ...</userinput></screen>
55 </tip>
Note: See TracBrowser for help on using the repository browser.