  Notes on the KDE-1.1 RPM Packages for Red Hat Linux
  The KDE Packaging Team, redhat-rpms@kde.org
  v1.14, 20 February 1999

  Information and quick installation instructions to accompany KDE-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/distribution/rpm/ in the
  RReeddHHaatt--44..22//ii338866, RReeddHHaatt--55..00--eeggccss//ii338866, RReeddHHaatt--55..11//ii338866, and
  RReeddHHaatt--55..22//ii338866 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.


  CChhaannggeess iinn tthhee KKDDEE--11..11 RRPPMM ppaacckkaaggeess.. 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-*.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.  It also installs (in /usr/sbin, which is
  in root's PATH) three scripts: iinnssttaallll--kkddee--11..11, iinnssttaallll--kkddee--11..11--aappppss,
  and uunniinnssttaallll--kkddee--11..11:


  +o  iinnssttaallll--kkddee--11..11 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  iinnssttaallll--kkddee--11..11--aappppss 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 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  uunniinnssttaallll--kkddee--11..11 is a script that uninstalls KDE-1.1.


     IIff yyoouu uussee tthheessee ssccrriippttss,, yyoouu wwiillll pprroobbaabbllyy nnoott nneeeedd ttoo rreeaadd tthhee
     rreesstt ooff tthhiiss ddooccuummeenntt,, wwhhiicchh ddeessccrriibbeess tthhee mmaannuuaall iinnssttaallllaattiioonn
     mmeetthhoodd!!



  +o  TThhrreeee distinct families of RPM packages, labelled "rrhh4422" (for Red
     Hat 4.2), "rrhh5500eeggccss" (for Red Hat 5.0) , and "rrhh55xx" (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-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 kkddee--aapppplliiccaattiioonnss--11..11--**rrhh**..ii338866..rrppmm
     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-*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 initial
     (required) kdesupport package; and documentation plus installation
     scripts are provided by the kdesupport-install-kde 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 distribution.   It is included here as
     "korganizer-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.  One
     such application is kpackage-1.1.2, a RPM (and Debian) Package
     Manager.


      11.. WWhhiicchh vveerrssiioonn ooff tthhee QQTT ttoooollkkiitt ttoo uussee??
        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.

        If a future QT-2.0 release maintains backwards compatibilty,
        appropriate qt-2.0-*rh*.i386.rpm RPM packages may work with
        these KDE-1.1 packages, but this cannot be guaranteed.


     22.. WWhhyy aarree tthheerree vvaarriioouuss ddiiffffeerreenntt sseettss ooff KKDDEE RRPPMM ppaacckkaaggeess??
        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 "rrhh4422" packages are for Red Hat 4.2, compiled with
        gcc-2.7.2.3 and libc5,

     +o  The "rrhh5500eeggccss" packages are for Red Hat 5.0, and are compiled
        with egcs-1.0.3a, glibc2, and libncurses-3.0

     +o  The "rrhh55xx" 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 nnoott 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).




     33.. TThhiinnggss ttoo ddoo bbeeffoorree iinnssttaalllliinngg tthhee RRPPMM ppaacckkaaggeess..
        (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/ 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 rreellooccaattaabbllee: 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 will need 30-40Mb 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 FFiillee
        HHeeiirraarrcchhyy SSttaannddaarrdd (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.  (DDoo tthhiiss BBEEFFOORREE iinnssttaalllliinngg KKDDEE !! ):

        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 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




     Now you can make symbolic links


          ln -sf kde-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 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-generated versions of these
     may not be compatible with the older KDE releases.) When you are
     happy with KDE-1.1, just delete the old KDE files with "\rm -rf
     /opt/kde-old".

     Note that uninstalling an older KDE will nnoott 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   IInn ppaarrttiiccuullaarr,, yyoouu mmaayy hhaavvee pprroobblleemmss oonn RReedd HHaatt 55..00//55..11//55..22 iiff
        yyoouu uuppggrraaddee ffrroomm kdesupport-1.0-*rh51, as the new
        kdesupport-1.1-*rh50egcs RPM package omits  libgdbm and libjpeg,
        and the kdesupport-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
        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 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 aafftteerr 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  RReemmoovvee aannyy ssppeecciiaall KKDDEE ccuussttoommiizzaattiioonnss iinn ssyysstteemm ffiilleess lliikkee
        /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.



     44aa.. IInnssttaallll lliibbppnngg--00..9966 iiff nneeeeddeedd ((RReedd HHaatt 44..22 oonnllyy))
        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.  They will also need to update to zgv-3.0-5rh42 (also
        supplied), as this depends on libpng.  TThheeyy wwiillll aallssoo nneeeedd ttoo
        uuppggrraaddee tthheeiirr vveerrssiioonn ooff 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
        ftp site.




     44bb.. IInnssttaallll lliibbssttddcc++++ iiff nneeeeddeedd ((RReedd HHaatt 55..00 oonnllyy))
        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 ggcccc__ttoo__eeggccss--
     HHOOWWTTOO for details (kdesupport installs it in /usr/doc/KDE-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.



     55.. IInnssttaalllliinngg tthhee RRPPMM ppaacckkaaggeess..
        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 kdesupport-install-kde, which makes documentation
     about installation on Red Hat available in /usr/doc/KDE-1.1:


          rpm -Uvh kdesupport-install-kde-1.1-*rh*.i386.rpm




     (It also installs scripts install-kde-1.1-base, install-
     kde-1.1-apps, and uninstall-kde-1.1, that automates most of the
     instructions given below).

     +o   IItt iiss rreeccoommmmeennddeedd yyoouu uussee tthheessee ssccrriippttss,, bbuutt iiff yyoouu wwiisshh ttoo
        iinnssttaallll ""mmaannuuaallllyy"",, ccoonnttiinnuuee wwiitthh tthhee iinnssttrruuccttiioonnss bbeellooww..

        Now install the KDE base system:

        First install kdesupport:


          rpm -Uvh kdesupport-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.  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-*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-*rh*.i386.rpm
     rpm -Uvh  kdelibs-1.1-*rh*.i386.rpm  --force
     rpm -Uvh  kdebase-1.1-*rh*.i386.rpm
     rpm -Uvh  kdebase-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)

     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-*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 con-
     tents of the package.   Before installation, you can get informa-
     tion about the contents of a package in your current directory with


          rpm -qip kde*-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 distribution.  A typical subpackage is kdenetwork-
     ppp-1.1-*rh*.i386.rpm which supplies the kppp application for set-
     ting up ppp network conections, while kdenetwork-
     tools-1.1-*rh*.i386.rpm supplies a subset of smaller utilities.

     This does not include the RPM packages which are not from an
     official KDE collection, but accompany the KDE packages.  The only
     such package which is currently part of the official KDE-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-*rh*.i386.rpm, requires installation of the the
     additional QwSpriteField support library, supplied by the RPM
     subpackage kdesupport-qwspritefield-1.1-*rh*-i386.rpm.



     66.. TThhiinnggss ttoo ddoo aafftteerr iinnssttaalllliinngg tthhee BBaassee RRPPMM ppaacckkaaggeess..
        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 two Red Hat configuration files
     (/etc/inittab, /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 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 IInnssttaallllaattiioonn GGuuiiddee, 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



































































