This howto will tell you the steps required to pull, build and install the GIT version of KPhotoAlbum in Ubuntu/Debian.
This will allow you to test all the latest features that have not been published in the official releases or have not reached your distribution yet. Alternatively, you may want to check out the nightly built Neon packages for kphotoalbum.
First, backup all your precious files!! See section "Backup" below.
Install all required packages (Ubuntu / Debian):
sudo apt install build-essential git sudo apt install cmake extra-cmake-modules kio-dev pkg-config pkg-kde-tools # if your distro ships a not too outdated version of kphotoalbum, you can replace the following with "sudo apt build-dep kphotoalbum" sudo apt install libexiv2-dev libjpeg-dev libkf5archive-dev libkf5config-dev libkf5coreaddons-dev libkf5i18n-dev libkf5iconthemes-dev libkf5jobwidgets-dev libkf5kdcraw-dev libkf5kgeomap-dev libkf5kipi-dev libkf5parts-dev libkf5widgetsaddons-dev libmarble-dev libphonon4qt5-dev libphonon4qt5experimental-dev libqt5webkit5-dev qtbase5-dev x11proto-core-dev libkf5doctools-dev gettext sudo apt install kipi-plugins ffmpeg
Notes on Ubuntu 16.04 LTS:
Preparations for other systems (openSUSE) - see at the bottom.
git clone git://anongit.kde.org/kphotoalbum cd kphotoalbum mkdir build ; cd build cmake -DCMAKE_INSTALL_PREFIX=~/.local -DCMAKE_BUILD_TYPE=RelWithDebInfo .. make make install
cd ~/kphotoalbum git pull make install
~/.local/bin/kpa-backup.sh --backup ~/.local/bin/kphotoalbum
If you've had KPhotoAlbum installed earlier from repositories, the Git KPhotoAlbum will use the same setting files as the earlier version. If you want to be able to use the previous version after installing this, please do install to custom directory, not the default one.
Install required build tools:
sudo apt install git build-essential cmake extra-cmake-modules kio-dev pkg-config pkg-kde-tools
Install required packages to build:
# if your distro ships a not too outdated version of kphotoalbum, you can replace the following with "sudo apt build-dep kphotoalbum" sudo apt install libexiv2-dev libjpeg-dev libkf5archive-dev libkf5config-dev libkf5coreaddons-dev libkf5i18n-dev libkf5iconthemes-dev libkf5jobwidgets-dev libkf5kdcraw-dev libkf5kgeomap-dev libkf5kipi-dev libkf5parts-dev libkf5widgetsaddons-dev libmarble-dev libphonon4qt5-dev libphonon4qt5experimental-dev libqt5webkit5-dev qtbase5-dev x11proto-core-dev libkf5doctools-dev
OPTIONAL BUT RECOMMENDED: Install other dependencies:
sudo apt install kipi-plugins ffmpeg
Clone the Git repository:
git clone git://anongit.kde.org/kphotoalbum.git
Move to the created directory
Create a build-directory (so you don't mess up you source directory)
mkdir build ; cd build
Run cmake to configure the build system
cmake ..[to install to the default directory]
You can adopt the configuration to your needs by adding additional arguments to cmake:
These options can just be added to the regular cmake command:
cmake -DCMAKE_INSTALL_PREFIX=/YOUR_INSTALL_PREFIX -DCMAKE_BUILD_TYPE=RelWithDebInfo ..
See the messages. In this stage you'll be told if you have missing dependencies. Do fix them (try to find the missing packages from the package repositories) before continuing.
This uses up to 4 processes to build kphotoalbum. On a modern system you may want to increase the number. If you want to use a single process only, simply omit the -j=4 entirely.
While you can install kphotoalbum to any directory of your choice, some directories make life easier for you. Here are some suggestions for your install prefix:
Both of the above suggestions are also searched by default when Qt searches for application resources. Using one of them makes sure that kphotoalbum can find its own resource files (e.g. the demo database).
Do not use /usr as prefix directory! This prefix is reserved for files managed by your distribution's package manager.
or if the installation path is not writable by your user:
sudo make install
If you have already installed a different version of kphotoalbum, and you only want to check out some specific feature, you may skip the installation step and directly run the kphotoalbum executable file in your build directory. Be aware, though, that in this case kphotoalbum uses the already installed resource files of your kphotoalbum installation. If there is not existing installation of kphotoalbum, certain features will not work correctly (demo database, HTML export, …)
If the install directory that you chose is not in your search path, your system won't find kphotoalbum on its own, or it may find a packaged version of kphotoalbum instead. To verify your installation, run:
The output should start with the install prefix that you chose earlier. If it does not match, you have to add the installation directory (/YOUR_INSTALL_PREFIX/bin) to your search path, or type the full path of the executable file.
Under most shells, you can add a directory to your search path using this command:
By using the latest GIT versions of KPhotoAlbum you risk losing your precious files. It shouldn't happen but you never know. This would now be an excellent time to run the backups - you've just downloaded a script to backup the KPhotoAlbum config files for you so keep reading! Your photos you already have backed up, right...?
To backup your database and configuration files, run:
Complete backup instructions can be found under #Backup
A handy feature of the cmake build-system is that it builds binaries in such a way that you can start them from within the build system. This certainly handy for quickly testing a new version of KPhotoalbum without touching anything else on your system. However, be aware that some features depend on hard-coded paths (e.g. menu-entries, Handbook, HTML Exports, Demo) and may not work as expected. These features will still use the files installed by the distributions version of KPhotoAlbum. You can just try out KPhotoalbum without installation first, and install later on (see 2.4), if you decide so.
If you installed to a non-standard directory, you have two options: 1a) Start KPhotoAlbum from the directory where it was installed:
OR 1b) add the following line to /home/username/.bashrc so you can start KPhotoAlbum from anywhere:
Restart your terminal (so that .bashrc gets executed)
It's always a good idea to first try out things with the demo-database. Just add "--demo" when starting KPhotoalbum:
In the kphotoalbum git directory, execute:
git pull cd build make -j4 make install
If you want to see what has changed try git log or qgit for graphical user interface.
If you upgraded your system and the build fails afterwards, it can often help to delete the build directory (no need to delete the source directory) and run the instructions under #Building again.
See http://kphotoalbum.org/index.php?page=compile for some more info on KIPI plugins, EXIF and video thumbnail support as well as Dutch/French handbook issues and KHelpCenter tips.
This text assumes that you already back up your image files (disk failures happen). When playing with an experimental version of kphotoalbum, you may also want to backup your image database and other files that are needed by kphotoalbum.
KPhotoalbum source code has a backup script included.
kpa-backup.sh --backup kpa-backup.sh --restore
If the backup script is not included in an old installation of kphotoalbum, you can run the backup script directly from the source directory:
script/kpa-backup.sh --backup script/kpa-backup.sh --restore
Create backup directory
Backup your settings:
cp -a ~/.local/share/kphotoalbum/kphotoalbumui.rc kpa-backup/ cp -a ~/.config/kphotoalbumrc kpa-backup/
And if you want to try KPhotoalbum with your real database (not the demo): Backup your database:
cp -a /path/to/your/image/folder/index.html kpa-backup/ cp -a /path/to/your/image/folder/exif-info.db kpa-backup/
Backup the layout of your Annotation dialog:
cp -a /path/to/your/image/folder/layout.dat kpa-backup/
These instructions were prepared with an out of the box installation of openSUSE Leap 42.2. Leap 42.1, SLES12 and Tumbleweed should work along the same lines. In older versions of openSUSE, success depends on the completeness of the transition to QT5 in the distribution. It is assumed that installation takes place from remote repositories (not from DVD).
Use settings->yast (command line: yast2) to install packages and patterns. You need root access to enter yast.
The easiest way to get all the necessary build tools is installing the pattern "KDE development":
Change to View->Search and search/select the libs AND the corresponding the *-devel packages:
Check the remaining toolkit (these packages should already be checked for installation or present anyhow). Search and check for installation:
Klick accept. Several more dependencies will be selected for installation. This is OK.
After installation it is advisable (not strictly necessary) to reboot.
Mplayer(1 or 2) is no longer necessary for video thumbnails if ffmpeg is available. In openSUSE only mplayer (1) is available as the Mplayer2 project lost support.
To get a complete set of supported codecs, it might be advisable to add the packman repository and install ffmpeg and vlc from there. The install of vlc will pull in a lot of codec libs:
Search and install vlc and ffmpeg: