https://bugs.kde.org/show_bug.cgi?id=379402
--- Comment #4 from caulier.gil...@gmail.com --- wildcowboy, the patch, as all patch in fact must be applied to source code and whole digiKam recompiled/installed. This require a complete compilation env, including compiler, linker, and shared libraries. Under Linux it's not too much complicated. All digiKam dependencies will be available de facto. The list is given here : https://cgit.kde.org/digikam-software-compilation.git/tree/DEPENDENCIES The basis to checkout all code is given here : https://cgit.kde.org/digikam-software-compilation.git/tree/README As you don't need a developer account to apply a patch (or create one), you can use the read only git repository. So typically it will be simplified as below : git clone git://anongit.kde.org/digikam-software-compilation.git .. and later run "download-repos" script. All the code will be downloaded from git server. After that you need to configure use the "bootstrap.linux" script and fix unresolved dependencies. When it's done, go to "build" directory and compile whole code with "make" If you have a multicore CPU "make -jxx" with xx the number of CPU to use will reduce a lots the compilation time. When it's done. apply the patch with the "patch -p1 < blabla.diff" command, in core sub-directory. Recompile digikam with make in build directory. Switch as root and run "make install/fast" in "build directory. Now digiKam is installed with patch on your system. This will overwrite the current version. So i recommend to use a cleaned VM dedicated for that. Voilà Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
