I will assume you are referring to 5.6-release. I will also assume you did not install filesets from a network, but installed them from CD or USB device. This is because if you install filesets from a network location, the installer will create
/etc/pkg.conf for you, pointing to the packages on the mirror you used during installation, so that you can run the
pkg_add(1) command without either creating the file yourself (see the
pkg.conf(5) man page) or using the PKG_PATH environment variable. My example uses the environment variable.
I will also assume you are using
amd64. You might be using i386 or sparc64, based on the panic you photographed and linked in your prior thread. If you are using one of these other architectures, please adjust the PKG_PATH environment variable accordingly.
Step 1. Export the PKG_PATH variable, pointing to the packages at your nearest mirror. You can find your nearest mirror
here.
# export PKG_PATH=http://<your nearest mirror>/pub/OpenBSD/5.6/packages/amd64/
Step 2. Install either the kde4-minimal installation, or the kde4 full installation. This example shows the full installation.
# pkg_add kde4
Here's the OpenBSD README file you get when you install either kde4 or kde4-minimal on 5.6-release:
Code:
+-----------------------------------------------------------------------
| Running kde4-4.13.3 on OpenBSD
+-----------------------------------------------------------------------
The KDE4 desktop can be installed using 2 different meta-packages:
* kde4-minimal, for a base KDE4 SC installation
* kde4, for a full KDE4 SC installation
They are focused on standard usage; i.e., development packages are left
out on purpose and can be installed via kdesdk and kdebindings packages.
Also, there is a kdegames meta-package which will install all games from
KDE4 SC.
Starting KDE4
==============
Before running startkde4(1), a system-wide D-Bus daemon needs to be
running ("dbus_daemon" needs to be added to the "pkg_scripts" variable
in rc.conf.local(8)):
# echo 'pkg_scripts="$pkg_scripts dbus_daemon"' >>/etc/rc.conf.local
Then the following line should be added:
exec /usr/local/bin/ck-launch-session /usr/local/bin/startkde4
... in ~/.xinitrc when using startx(1) (console login)
... in ~/.xsession when using xdm(1) (X Display Manager login)
Profile location
================
By default, KDE 4 in OpenBSD looks for ~/.kde4. You can override this
by setting up KDEHOME environment variable, but please note that KDE 3
uses this variable, too. On the bright side, KDE 3 and 4 profiles are
mostly compatible: KDE 4 apps that change storage or config format,
usually create their own copy using the new format in a separate place,
so in the worst case you'll have some settings duplicated and not
shared.
Renamed binaries
================
Some executable files in /usr/local/bin directory were renamed
by adding the "4" suffix to avoid clashes with KDE 3 ones, namely:
* kdebugdialog
* khelpcenter
* kjscmd
* kreadconfig
* kstart
* ktrash
* kwriteconfig
The third party programs or scripts that rely on "standard" names
will obviously fail. So beware of blind running foreign scripts
(you shouldn't be doing this in the first place, though, if you're
running OpenBSD), the best could happen is that they will tweak
your KDE3 setup instead.
mDNS/DNS-SD support
===================
The avahi-daemon(8) daemon provides Zeroconf support (aka. Bonjour /
Rendezvous) in KDE.
To make use of it multicasting should be enabled, and "avahi_daemon"
needs to be added to the "pkg_scripts" variable _after_ "dbus_daemon":
# echo 'multicast_host=YES' >>/etc/rc.conf.local
# echo 'pkg_scripts="$pkg_scripts dbus_daemon avahi_daemon"' >>/etc/rc.conf.local