BlueDevil runtime dependencies: -bluez5 -General Bluetooth management
-bluez-obexd -Be able to "Browse File" aka kio_obexftp -Be able to "Send Files" (bluedevil-sendfile) -Be able to receive files
-pulseaudio-module-bluetooth -Be able to connect A2DP profile

# Branding ## CMake Use CMake to set the common overridden variables. ``` cmake -DDISTRO_NAME=KDistro -DDISTRO_VERSION=123 -DDISTRO_LOGO=kdistro -DBACKGROUND_TOP_COLOR=kdistro_green -DBACKGROUND_BOTTOM_COLOR=kdistro_blue .. ```

SEE ALSO: README

Ksshaskpass is a front-end for ssh-add which stores the password of the sh key in KWallet. Ksshaskpass is not meant to be executed directly, you need to tell ssh-add about it. ssh-add will then call it if it is not associated to a terminal. From the ssh-add manpage: / | DISPLAY and SSH_ASKPASS | If ssh-add needs a passphrase, it will read the passphrase from the | current terminal if it was run from a terminal. If ssh-add does not | have a terminal associated with it but DISPLAY and SSH_ASKPASS are | set, it will execute the program specified by SSH_ASKPASS and open | an X11 window to read the passphrase. This is particularly useful | when calling ssh-add from a .xsession or related script. (Note that | on some machines it may be necessary to redirect the input from | /dev/null to make this work.) \ This means you need to make sure to set the SSH_ASKPASS environment variable to the path of ksshaskpass and then call ssh-add from your autostart scripts.

SEE ALSO: README

How kwallet-pam works:
During the pam "auth" (pam_authenticate) stage the module gets the password in plain text. It hashes it against a random salt previously generated by kwallet of random data and keeps it in memory.
When we get to the "session" (pam_open_session) stage the pam module forks and launches kwalletd as the user with file descriptor AND a socket. We send the salted password over the file descriptor after forking and write the socket address to an env variable.
KWalletd recieves the pre-hashed key and then sits there doing nothing. (before the QApplication constructor)
Later after session startup (autostart apps phase 0) a small script passes the newly set environment from the user session to kwalletd over the socket.
kwalletd receives this, sets the environment variables and continues into the normal bootup.
The session env is needed as if we launch pre session various important env vars are not set and kwalletd is a graphical app.

In order to build this repository, you need to clone the following submodules (as the current KDE git infrastructure does not support submodules)
[submodule "3rdparty/azmq"] path = 3rdparty/azmq url = https://github.com/zeromq/azmq
You can do it by executing the following from the repository root:
mkdir 3rdparty git clone https://github.com/zeromq/azmq 3rdparty/azmq
The Boost libraries are not provided in the 3rdparty directory, the build relies on you having Boost 1.67 or greater installed on your system. If Boost is not found, you can pass a custom BOOST_ROOT value to cmake.

Oxygen-Gtk is a port of the default KDE widget theme (Oxygen), to gtk.
It's primary goal is to ensure visual consistency between gtk and qt-based applications running under kde. A secondary objective is to also have a stand-alone nice looking gtk theme that would behave well on other Desktop Environments.
Unlike other attempts made to port the kde oxygen theme to gtk, this attempt does not depend on Qt (via some Qt to Gtk conversion engine), nor does render the widget appearance via hard coded pixmaps, which otherwise breaks everytime some setting is changed in kde.
Contents:
I. Introduction

SEE ALSO: README

See README.developers and README.packagers (the former is also for users).
In order to properly display the files, use the GNU man command.
man README.developers man README.packagers

to build:
mkdir build cd build cmake .. -DCMAKE_INSTALL_PREFIX=`kf5-config --prefix` make install

Smaragd
Smaragd is a themable window decoration engine for KDE's KWin window manager. It uses the original Emerald engines to render the decorations to support all current Emerald themes.
Read INSTALL for installation and NOTES for usage hints.
See individual files for Copyright information.