DIGIKAM DEEP-LEARNING MODEL FILES REPOSITORY
============================================

digiKam uses huge deep-learning files for faces management, aesthetic contents detector, and auto-tags engines.
These files are not includes in source code tarball and are loaded in demand at run-time.
Files are hosted in these sub-directories:

- aestheticdetector/
- autotags/
- facesengine/

DIGIKAM EXIFTOOL ROLLING RELEASE REPOSITORY
===========================================

ExifTool project do not host a repository of archives to the rolling release of the public tarball.
To allows to build the digiKam bundles tested with a specific version of ExifTool the exiftool/ subdirectory
host the current validated tarballs. Updating file is done with the update_exiftool.sh script:

https://invent.kde.org/graphics/digikam/-/blob/master/project/scripts/update_exiftool.sh?ref_type=heads

DIGIKAM CONTINUOUS INTEGRATION REPORTS
======================================

In the reports/ sub-directory are hosted the archives generated by the static codes analyzers runs over
the whole code of digiKam. Scripts used to generated these reports are hosted here:

https://invent.kde.org/graphics/digikam/-/tree/master/project/reports?ref_type=heads

DIGIKAM WEEKLY PRE-VERSION BUNDLES REPOSITORY FOR TESTING
=========================================================

The bundle files provided in this repository are built weekly and can be used to test new features quickly.
Do not use these versions in production, unless you know what are you doing.

Linux universal AppImage bundles:
---------------------------------

* digiKam-version-timestamp-x86-64-Qtversion.appimage        => for Linux 64 bits.
* digiKam-version-timestamp-x86-64-Qtversion-debug.appimage  => for Linux 64 bits with debug symbols.

These bundles are compatible with all Linux distributions which support Fuse file system.
It must be runnable on all distributions older than 3/4 years.

Make file executable and run it as well. Nothing is installed and do not require root rights.
See here for details : http://askubuntu.com/questions/774490/what-is-an-appimage-how-do-i-install-it

Bundle executable can take arguments to run:

 without option       : run digiKam.
 <showfoto>           : run Showfoto instead digiKam.
 <debug>              : run digiKam into GDB (only suitable with appimage compiled with debug symbols).
 <debug> <showfoto>   : run Showfoto into GDB  (only suitable with appimage compiled with debug symbols).
 <help>               : show these information.


Windows bundle installers:
--------------------------

* digiKam-version-timestamp-win64.exe              => for Windows 64 bits.
* digiKam-version-timestamp-win64-debug.exe        => for Windows 64 bits with debug symbols.

These bundles based on Qt6 are built with Microsoft VCPKG environnement.
They do not require extra Microsoft run-time libraries and are compatible with Windows >= 10.

Windows Portable archives:
--------------------------

* digiKam-version-timestamp-win64.tar.xz           => for Windows 64 bits.
* digiKam-version-timestamp-win64-debug.tar.xz     => for Windows 64 bits with debug symbols.

Self archives of Windows installer contents to make Portable versions of digiKam.
This do not requires admin rights to install digiKam in your Windows home directory as well.

MacOS bundle package:
---------------------

* digiKam-version-timestamp-MacOS-x86-64.pkg       => for MacOS 64 bits.
* digiKam-version-timestamp-MacOS-x86-64-debug.pkg => for MacOS 64 bits with debug symbols.

These Qt5 based bundles are built with Macports for Intel computers with backward compatibility to macOS 10.13.
They can be used with Apple Silicon based computers with Rosetta 2 emulator.


Notes :
-------

* To know the file SHA256 check-sums, use this kind of url:
  https://files.kde.org/digikam/_bundle_file_name_.sha256
  They can be used to verify if bundles files downloaded are corrupted or not.

* The bundle build-timestamp included in file name follow this ISO scheme : YYYYMMTDDhhmmss, with
  Y : year
  M : month
  D : day
  T : separator
  h : hour
  m : minute
  s : seconds

* Bundles name with '-debug' suffix are compiled with full debug symbols. File sizes are more heavy
  but it's possible to run application in debugger and to report dysfunctions to developpers with a
  backtrace to hack and fix quickly the problems. See Contributes web project page for details:
  https://www.digikam.org/contribute/

* The Qt version 6 of the bundles must be prefered to the Qt version 5 if available.
  Qt5 bundles are hosted in legacy/ sub-directory.

* The bundles continuous deployement log files compressed with gzip are stored in build.logs/ sub-directory.