home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
WordPerfect for Linux Bible
/
WP4LinuxBible.iso
/
KDE_Red_Hat
/
readme-redhat-rpms.txt
< prev
next >
Wrap
Text File
|
1999-05-03
|
26KB
|
661 lines
Notes on the KDE-1.1.1 RPM Packages for Red Hat Linux
The KDE Packaging Team, redhat-rpms@kde.org
v1.15, 22 April 1999
Information and quick installation instructions to accompany KDE-1.1.1
"rh42", "rh50egcs" and "rh5x" packages for Red Hat Linux 4.2, 5.0, 5.1
and 5.2, available at ftp.kde.org.
The i386 versions of these RPM packages are available at
ftp://ftp.kde.org/pub/kde/stable/1.1.1/distribution/rpm/ in the
RReeddHHaatt--44..22//ii338866, RReeddHHaatt--55..00eeggccss//ii338866, RReeddHHaatt--55..11//ii338866, and
RReeddHHaatt--55..22//ii338866 subdirectories. RPM packages for other architectures
may be available; substitute the architecture name (e.g, alpha) for
i386 in these instructions,
Red Hat RPM packages mentioned here can be found at Red Hat's ftp site
ftp://ftp.redhat.com/pub/redhat/ or at mirror sites listed in
http://www.redhat.com/mirrors.html.
CChhaannggeess iinn tthhee KKDDEE--11..11..11 RRPPMM ppaacckkaaggeess.. If you have previously
installed KDE RPM packages for Red Hat, you will notice many new
packaging features (as well as improvements in KDE itself):
+o New installation scripts: The first RPM package you should install
is kde-installer:
rpm -Uvh kde-installer-1.1.1-*.i386.rpm
This will install a set of documents (including this one) describing
all aspects of the installation process, and giving troubleshooting
hints, in /usr/doc/KDE-1.1.1. It also installs (in /usr/sbin, which
is in root's PATH) three scripts: iinnssttaallll--kkddee--11..11..11, iinnssttaallll--
kkddee--11..11..11--aappppss, and uunniinnssttaallll--kkddee:
+o iinnssttaallll--kkddee--11..11..11 is a script that handles all aspects of the
installation process: installing the base packages, configuring kdm
and user accounts, and installing optional applications.
+o NEW: It can now be invoked with a "default" option:
install-kde-1.1.1 default
which carries out a default installation without requiring user input
from the terminal (it must be run in a directory containing the RPM
packages). This allows automated installations. You can supply a list
of users to give KDE desktops to in a file userlist.kde. You can also
control which optional applications are or are not installed with
lists in files include_app.kde and exclude_app.kde. Run ``install-
kde-1.1.1 help '' for more information.
+o iinnssttaallll--kkddee--11..11..11--aappppss is a script that handles installation of
optional applications after the base packages have been installed.
It can be run at any time (install-kde-1.1.1 calls it to finish the
installation process), and allows you to review the descriptions of
the various KDE application RPM packages, and decide which to
install.
+o uunniinnssttaallll--kkddee is a script that uninstalls a RPM-based KDE
installation.
IIff yyoouu uussee tthheessee ssccrriippttss,, yyoouu wwiillll pprroobbaabbllyy nnoott nneeeedd ttoo rreeaadd tthhee
rreesstt ooff tthhiiss ddooccuummeenntt,, wwhhiicchh ddeessccrriibbeess tthhee mmaannuuaall iinnssttaallllaattiioonn
mmeetthhoodd!!
+o TThhrreeee distinct families of RPM packages, labelled "rrhh4422" (for Red
Hat 4.2), "rrhh5500eeggccss" (for Red Hat 5.0) , and "rrhh55xx" (for Red Hat
5.1/5.2) replace the single family of KDE-1.0 "rh51" RPM packages
built for Red Hat 5.0/5.1/5.2.
+o The RPM packages are now "relocatable" (can be installed to a
location different from the default $KDEDIR = /opt/kde). The
configuration scripts are automatically adjusted to the location
used when rpm installs the packages.
+o The KDE applications from the various optional application
collections are now distributed as separate RPM subpackages, (for
example, kdenetwork-ppp-1.1.1-1rh5x.i386.rpm, now provides the kppp
component of the kdenetwork collection) giving you maximum
flexibility to choose which optional KDE components to install on
your system.
+o For convenience, these optional application RPM packages are also
distributed in a single large kkddee--aapppplliiccaattiioonnss--11..11..11--**rrhh**..ii338866..rrppmm
RPM package which, when installed, just places the collection of
individual RPM packages in /usr/src/redhat/RPMS/i386, (or wherever
desired, for example in /usr/local/KDE/RPMS, using
rpm -Uvh kde-applications-1.1.1-*rh*-i386.rpm --prefix /usr/local/KDE/RPMS
to relocate the files).
(The required kdelibs and kdebase packages remain monolithic.)
+o The kdesupport package no longer provides the libgdbm, libjpeg and
libgif libraries, if they are provided by the corresponding Red Hat
distribution. The libQwSpriteField library (needed only by the
game kasteroid) is moved to a subpackage.
+o All KDE Red Hat support scripts are now supplied by the (required)
kdesupport package; and documentation plus installation scripts are
provided by the kde-installer package. This is the first package
that should be installed.
+o When KDE configuration files are not present in a user's directory,
the .Xclients script which automatically starts KDE now installs a
consistent default configuration from "skeleton" files in
$KDEDIR/etc/skel. The default initial KDE Desktop seen by a new
KDE user includes the "Welcome to KDE" screen of kdehelp. The
System manager can modify the location the default KDE
configuration is taken from, to supply a locally-customized default
KDE Desktop. (This is a feature special to the RPM packages, not
found in "tarball" KDE.)
+o The standalone KDE application korganizer has become part of the
"official" KDE-1.1.1 distribution. It is included here as
"korganizer-1.1.1-*rh*.i386.rpm". Other selected KDE applications
that are not part of the "Official" KDE-1.1 release may be added to
this RPM collection if the Packagers judge them to be stable. So
far, these include:
+o kpackage-1.2.1, a RPM (and Debian) Package Manager. (supplied by
the kdeadmin-kpackage RPM package).
+o kdf-0.5.1, a disk utilization and management tool (supplied by the
kdeutils-diskfree RPM package).
+o kclock-0.6, an analog/digital clock (an extra component in the
kdeutils-tools RPM package).
+o ktalk-0.2.7, a talk client (an extra component in the kdenetwork-
talk RPM package).
11.. WWhhiicchh vveerrssiioonn ooff tthhee QQTT ttoooollkkiitt ttoo uussee??
These rpms are built to use QT v1.42. The rpm packages should
be available where you obtain the KDE rpms; if not, look for
them at ftp://ftp.troll.no/pub/contrib/qt-packages/linux
For RH4.2 (Red Hat 4.2), get the RPM package
qt-1.42-1rh42.i386.rpm. This is compiled with gcc-2.7.2.3 and
libc5.
For RH5.0, RH5.1, or RH5.2, get the RPM package
qt-1.42-3rh51.i386.rpm. This is compiled with egcs-1.0.3a and
glibc2. (For those who requested it, this package now includes
the qimageio extension.)
If you plan to compile additional KDE applications, also obtain
the corresponding qt-devel RPM package.
These packages will also work with qt-1.44, provided it has been
compiled to enable GIF graphics file support (this is disabled
by default in qt-1.44, because of the Unisys/LZW patent issue).
They will nnoott work with qt-2.0.
22.. WWhhyy aarree tthheerree vvaarriioouuss ddiiffffeerreenntt sseettss ooff KKDDEE RRPPMM ppaacckkaaggeess??
The evolution of the Red Hat distribution means that there are
binary incompatibilities between different releases (except
between RH5.1 and RH5.2, which use the same RPM package).
+o The "rrhh4422" packages are for Red Hat 4.2, compiled with
gcc-2.7.2.3 and libc5,
+o The "rrhh5500eeggccss" packages are for Red Hat 5.0, and are compiled
with egcs-1.0.3a, glibc2, and libncurses-3.0
+o The "rrhh55xx" packages are for Red Hat 5.1 and 5.2, and are
compiled with egcs-1.0.3a, glibc2, and libncurses-4.0.
Since the "rh50egcs" RPM packages are nnoott compiled with the
gcc-2.7.2.3 compiler supplied with RH5.0, they require that the
C++ library libstdc++-2.8.0 taken from the Red Hat 5.1 or 5.2
distribution is added to your RH5.0 installation. (KDE RPM
packages for RH5.0 compiled with the gcc-2.7.2.3 compiler and
glibc2 currently have broken PAM support, and will not be
released unless this is fixed). (NNoottee.. ((44//11999999)) TThheerree aarree
rreeppoorrttss tthhaatt tthhiiss bbuugg jjuusstt nnooww wweenntt aawwaayy aass aa hhaappppyy ccoonnsseeqquueennccee
ooff aa ddiiffffeerreenntt bbuuggffiixx!!))
33.. TThhiinnggss ttoo ddoo bbeeffoorree iinnssttaalllliinngg tthhee RRPPMM ppaacckkaaggeess..
(For more information, see the Installation Guide for the KDE
RPM packages for Red Hat Linux; this will be available in
/usr/doc/KDE-1.1.1/ after the kdesupport RPM package is
installed).
_O_N_L_Y _I_N_S_T_A_L_L _K_D_E _I_F _Y_O_U _C_U_R_R_E_N_T_L_Y _H_A_V_E _A _W_O_R_K_I_N_G _X _W_I_N_D_O_W _S_Y_S_T_E_M
_O_N _Y_O_U_R _R_E_D _H_A_T _S_Y_S_T_E_M_. _F_I_X _A_N_Y _P_R_O_B_L_E_M_S _W_I_T_H _"_X_" _B_E_F_O_R_E
_I_N_S_T_A_L_L_I_N_G _K_D_E_.
Then login as the superuser (root).
The standard KDE installation is in $KDEDIR = /opt/kde, but the
RPM packages are rreellooccaattaabbllee: you can install them to another
location such as /usr/kde with the rpm ... --prefix=/usr/kde
option. If you use this option, you will have to make sure that
any KDE applications you later install that are not part of this
distribution install to the correct location. You can probbably
fix any such problems by making /opt/kde a symbolic link to the
actual $KDEDIR location.
You will need about 50MB disk space for a full KDE installation.
Type "df" to see available space (in Kb) on your disk
partitions.
Ideally, /opt is the mount point of a separate partition, but
this is not part of the current Linux File System Standard
followed by Red Hat. (It is however part of the new FFiillee
HHeeiirraarrcchhyy SSttaannddaarrdd (FHS) v2.0, which has been announced to be
part of the forthcoming Linux Standard Base (LSB) standard). If
you do not have (or do not wish to create) an /opt partition,
(and do not wish to relocate the RPM packages), you can either:
1. Do nothing: in this case, KDE will install to a directory
/opt/kde on the root partition /. (If not enough space is
available, this may cause problems by filling your root
partition!)
2. Create a directory /opt, and make /opt/kde a symbolic link to
a directory on a partition with free space, e.g.:
mkdir /opt
mkdir /usr/local/kde
ln -s ../usr/local/kde /opt/kde
This provides the greatest flexibility, as other packages that
install to /opt can be then be placed on different partitions
using symbolic links. (DDoo tthhiiss BBEEFFOORREE iinnssttaalllliinngg KKDDEE !! ):
If you have an older version of KDE installed we strongly
recommend that you should uninstall if it is older than KDE-1.1
(or move it out of the way so the installation to /opt/kde will
be clean).
+o Tip: if you wish to see whether KDE-1.1.1 works for you, before
removing your older KDE installation (installed in /opt/kde),
just
mv /opt/kde /opt/kde-old
When you now use RPM to erase or update KDE, your old KDE files
will remain safe in /opt/kde-old (rpm may issue lots of warning
messages that files it is trying to erase do not exist, but this is
harmless.) If after installing KDE-1.1, you wish to return to the
older KDE, just
mv /opt/kde /opt/kde-1.1.1
Now you can make symbolic links
ln -sf kde-1.1.1 /opt/kde
or
ln -sf kde-old /opt/kde
to choose which version of KDE you run. (The .Xclients script that
the KDE-1.1.1 usekde script installs in a user's home directory
should work with older KDE installations; if you switch back to the
older KDE, it is possible that users may have to move or delete
some or all of their configuration files and directories ~/.kderc,
~/.kde and ~/Desktop, as the KDE-1.1.1-generated versions of these
may not be compatible with the older KDE releases.) When you are
happy with KDE-1.1.1, just delete the old KDE files with "\rm -rf
/opt/kde-old".
Note that uninstalling an older KDE will nnoott affect users' personal
KDE settings, which are stored in their home directory in the
~/.kde/ directory tree (and in a file ~/.kderc). However, if these
personal settings are from an older version of KDE, and KDE does
not run properly, users may need to move their ~/.kderc file and
~/.kde/, and ~/Desktop/ directories out of the way, so a new
default KDE configuration is installed when they start KDE, and
then transfer those old settings they want to keep to the new KDE
configuration.
+o IInn ppaarrttiiccuullaarr,, yyoouu mmaayy hhaavvee pprroobblleemmss oonn RReedd HHaatt 55..00//55..11//55..22 iiff
yyoouu uuppggrraaddee ffrroomm kdesupport-1.0-*rh51, as the new
kdesupport-1.1.1-*rh50egcs RPM package omits libgdbm and
libjpeg, and the kdesupport-1.1.1-*rh5x RPM package omits libgif
as well. It was our decision that you should rely on Red Hat's
own libgdbm, libjpeg, and libungif RPM packages for these
libraries. (Since various KDE-1.0 "rh51" RPM packages rely on
the versions of these libraries supplied in the KDE-1.0
kdesupport package, they will resist your attempt to upgrade to
the KDE-1.1.1 kdesupport RPM package, as their required
libraries would be lost; the best solution is to remove these
KDE-1.0 RPMS with rpm -e before installing the KDE-1.1.1 RPMS.)
+o For various reasons, it is also recommended that you use rpm to
remove any pre-release RPM packages of KDE-1.1 before upgrading.
When rpm upgrades a package, the "uninstall" RPM scripts of the
old package being removed run _a_f_t_e_r the "install" RPM scripts of
the new package, and may mess up the newly installed package if
they were not designed properly. (rpm only removes the old RPM
package aafftteerr the successful installation of the new package has
been verified.) By their nature, pre-release versions may not be
designed correctly, and this did happen with the KDE-1.1pre1
RPM's.
Red Hat 4.2 users (rh50egcs RPMS) must make sure the Red Hat RPM
package gdbm is installed.
Red Hat 5.0 users (rh50egcs RPMS) must make sure the Red Hat RPM
packages gdbm and libjpeg-6a are installed.
Red Hat 5.1/5.2 users (rh5x RPMS) must make sure the Red Hat
RPM packages gdbm, libjpeg-6b, and libungif are installed. (For
Red Hat 5.1, the last two packages must be the updated RPM
packages found at Red Hat's ftp site
ftp://ftp.redhat.com/pub/redhat/updates/5.1/i386/jpeg/ in the
jpeg subdirectory of the Red Hat 5.1 updates).
+o RReemmoovvee aannyy ssppeecciiaall KKDDEE ccuussttoommiizzaattiioonnss iinn ssyysstteemm ffiilleess lliikkee
/etc/profile to set KDEDIR, put KDE executables in the system
path, etc. This will be handled automatically by this
installation (by scripts in /etc/profile.d), and your older
customizations may interfere with this.
44aa.. IInnssttaallll lliibbppnngg--11..00..11 iiff nneeeeddeedd ((RReedd HHaatt 44..22 oonnllyy))
Red Hat 4.2 users need a newer version of libpng than that
supplied by Red Hat. The KDE Packaging Team provides RPM
packages libpng-1.0.1-5rh42 and libpng-devel-1.0.1-5rh42 (taken
from RedHat 5.2 and rebuilt on Red Hat 4.2) with the KDE "rh42"
RPMS. If they are using zgv they will also need to update to
zgv-3.0-5rh42 (also supplied), as this depends on libpng. TThheeyy
wwiillll aallssoo nneeeedd ttoo uuppggrraaddee tthheeiirr vveerrssiioonn ooff rpm to 2.5 or
greater. (rpm-2.3.11 which was part of the original Red Hat 4.2
distribution will not work with these RPM packages). Updates
are available at Red Hat's ftp site.
44bb.. IInnssttaallll lliibbssttddcc++++ iiff nneeeeddeedd ((RReedd HHaatt 55..00 oonnllyy))
Red Hat 5.0 users need to obtain the libstdc++-2.8.0 RPM package
from the Red Hat 5.2 (or 5.1) distribution, and install it on
their Red Hat 5.0 system. They will also need to upgrade their
version of rpm to 2.5 or greater. (rpm-2.4.10 which was part of
the original Red Hat 5.0 distribution will not work with these
RPM packages).
Get it from
ftp://ftp.redhat.com/pub/redhat/redhat-5.2/i386/RedHat/RPMS/libstdc++-2.8.0-14.i386.rpm
and install it:
rpm -Uvh libstdc++-2.8.0-*.i386.rpm
If you intend to compile KDE applications for your Red Hat 5.0
system, you will also need to install the egcs-1.0.3a compiler from
the Red Hat 5.2 distribution (or the egcs-1.0.2 compiler from Red
Hat 5.1) on your Red Hat 5.0 system. See the document ggcccc__ttoo__eeggccss--
HHOOWWTTOO for details (kdesupport installs it in /usr/doc/KDE-1.1.1).
If you are still using Red Hat 5.0 (Red Hat's first glibc release)
you should seriously consider upgrading to Red Hat 5.2.
55.. IInnssttaalllliinngg tthhee RRPPMM ppaacckkaaggeess..
From the directory that contains the RPM packages: First install
QT:
rpm -Uvh qt-1.42-*rh*.i386.rpm
where *rh* is 1rh42 for RH4.2, and 3rh51 for RH5.0, RH5.1 and
RH5.2. Also install the corresponding qt-devel RPM package if you
plan to compile any KDE applications.
Next, install kde-installer, which makes documentation about
installation on Red Hat available in /usr/doc/KDE-1.1.1:
rpm -Uvh kde-installer-1.1.1-*rh*.i386.rpm
(It also installs scripts install-kde-1.1.1, install-
kde-1.1.1-apps, and uninstall-kde, that automates most of the
instructions given below).
+o IItt iiss rreeccoommmmeennddeedd yyoouu uussee tthheessee ssccrriippttss,, bbuutt iiff yyoouu wwiisshh ttoo
iinnssttaallll ""mmaannuuaallllyy"",, ccoonnttiinnuuee wwiitthh tthhee iinnssttrruuccttiioonnss bbeellooww..
Now install the KDE base system:
First install kdesupport:
rpm -Uvh kdesupport-1.1.1-*rh*.i386.rpm
where *rh* is *rh42 for RH4.2, *rh50egcs for RH5.0, and *rh5x for
RH5.1, RH5.2. Once this is installed, you will have access to the
KDE-Red-Hat-support documents in /usr/doc/KDE-1.1.1. If you are
upgrading from earlier KDE RPM packages (including 1.1pre
releases), that you did not first uninstall, repeat this step with
rpm -Uvh kdesupport-1.1.1-*rh*.i386.rpm --force
Now login again as root (important!), and type
env
In the output of env, you should see PATH=/opt/kde/bin:... and
KDEDIR=/opt/kde. (If you are relocating the KDE files to say,
/usr/kde, using
rpm -Uvh .... --prefix=/usr/kde
the output of env will reflect yout relocated prefix; you will need
to use the --prefix= option for each RPM package you install.)
Continue the installation with
rpm -Uvh kdelibs-1.1.1-*rh*.i386.rpm
rpm -Uvh kdelibs-1.1.1-*rh*.i386.rpm --force
rpm -Uvh kdebase-1.1.1-*rh*.i386.rpm
rpm -Uvh kdebase-1.1.1-*rh*.i386.rpm --force
(The second, forced reinstallation of each RPM package is unneces-
sary unless you are upgrading over an installed older KDE release).
If anything about your KDE installation seems wrong, your first fix
should be to try such a forced reinstallation of the base distribu-
tion (also look in the troubleshooting section of the installation
guide in /usr/doc/KDE-1.1.1)
This completes the installation of the Base KDE distribution. If
you wish, continue with installation of optional KDE components, or
do this later.
Now install the optional KDE RPM packages
rpm -Uvh kde*-1.1.1-*rh*.i386.rpm
where kde* is any of: kdeadmin*, kdegames*, kdegraphics*, kdemulti-
media*, kdenetwork*, kdetoys*, kdeutils*, or kdeapps*. The "*" in
these package names is a (hopefully) explanatory name for the
contents of the package. Before installation, you can get infor-
mation about the contents of a package in your current directory
with
rpm -qip kde*-1.1.1-*rh*.i386.rpm
Most of these packages are subpackages from the seven collections
of optional KDE applications that, with the Base distribution, make
up the KDE-1.1.1 distribution. A typical subpackage is kdenetwork-
ppp-1.1.1-*rh*.i386.rpm which supplies the kppp application for
setting up ppp network conections, while kdenetwork-
tools-1.1.1-*rh*.i386.rpm supplies a subset of smaller utilities.
This does not include the RPM packages of standalone applications.
The only such package which is currently part of the official
KDE-1.1.1 distribution is the calendar and appointment scheduling
application korganizer. However, other KDE applications which are
believed to be stable ("non-beta") may be included by the KDE
Packaging Team.
Finally, at least one official KDE application, the game kdegames-
asteroids-1.1.1-*rh*.i386.rpm, requires installation of the the
additional QwSpriteField support library, supplied by the RPM
subpackage kdesupport-qwspritefield-1.1.1-*rh*-i386.rpm.
66.. TThhiinnggss ttoo ddoo aafftteerr iinnssttaalllliinngg tthhee BBaassee RRPPMM ppaacckkaaggeess..
To use the KDE X Display Manager kdm as a substitute for xdm,
type
/opt/kde/bin/kdm_on
kdm_on makes small changes to four Red Hat configuration files
(/etc/inittab, /etc/X11/xdm/GiveConsole /etc/X11/xdm/TakeConsole
/etc/X11/xdm/Xsetup_0 ). (These changes can be reversed by typing
"/opt/kde/bin/kdm_off"). If the system is already running xdm in
runlevel 5, (and no X Window sessions are active) type
telinit 3 ; telinit 5
to shut down xdm and start kdm.
For each user who wants to use KDE as their desktop, type
/opt/kde/bin/usekde <username>
(Users may also do this for themselves by just typing "usekde"
after they next log in.) A hidden file .Xclients installed in the
user's home directory starts the KDE desktop in their next X Window
session; they can simply delete this file in the (unlikely) event
that they no longer wish to use KDE.
+o Note that when a user starts KDE, .Xclients runs a script
kdesetup, which checks whether the user's home directory
contains the configuration file ~/.kderc, and directories
~/.kde, ~/Desktop. If any of these do not exist, copies of
their defaults are installed before KDE starts. If they exist,
but are from an older KDE installation, the user may wish to
move them out of the way, to allow the new KDE-1.1.1 default
versions to be installed when KDE next starts.
It is also simple to configure the system so all users use a
KDE desktop by default, and to customize the initial KDE desktop
that they see. For details, see IInnssttaallllaattiioonn GGuuiiddee, which also
includes troubleshooting hints, and is installed by the
kdesupport RPM package into /usr/doc/KDE-1.0, along with other
Red Hat-specific documentation.
The KDE configuration initially installed by these RPM packages
places icons for printing, and for mounting/unmounting floppy-
disk and cdrom drives on the desktop. The System Manager must
ensure these are correctly configured for the system before they
will work (or delete them if they are not wanted). The System
Manager may wish to customize the default KDE Desktop for the
system; see the Installation Guide for more details.
Now enjoy KDE on your Red Hat system next time you open an X Window
session!
The KDE Packaging Team
Send comments or corrections to: redhat-rpms@kde.org