source: archive/kde/kde-intro.xml@ 45f56ac

10.0 10.1 11.0 11.1 11.2 11.3 12.0 7.10 7.4 7.5 7.6 7.6-blfs 7.6-systemd 7.7 7.8 7.9 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind gnome kde5-13430 kde5-14269 kde5-14686 kea ken/inkscape-core-mods krejzi/svn lazarus lxqt nosym perl-modules plabs/python-mods qt5new systemd-11177 systemd-13485 trunk upgradedb xry111/intltool xry111/soup3 xry111/test-20220226 xry111/xf86-video-removal
Last change on this file since 45f56ac was 0d7900a, checked in by Randy McMurchy <randy@…>, 11 years ago

Removed extraneous spaces from blank lines and at the end of lines in the .xml

git-svn-id: svn:// af4574ff-66df-0310-9fd7-8a98e5e911e0

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