<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Dear Gilles and Remo,</p>
<p>Thank you for your replies. <br>
</p>
<p>Sorry for any confusion, yes I am at this point not looking at
compiling from sources.</p>
<p>Looking at –<br>
</p>
<blockquote>
<pre class="moz-quote-pre" wrap=""><a class="moz-txt-link-freetext" href="https://docs.digikam.org/en/getting_started/installation.html#configuration-files">https://docs.digikam.org/en/getting_started/installation.html#configuration-files</a></pre>
</blockquote>
<p></p>
<p>I see that even with a windows binary tarball "install", the
application will use standard windows profile locations to keep
the configuration files.</p>
<p>Is there any way to ask Digikam to store these locally within its
own folder structure? <br>
Perhaps by using a switch on starting Digikam on the command-line
or in a shortcut link? <br>
</p>
<p>Something like:</p>
<blockquote>
<p>w:\digikam\digikam.exe /runlocal<br>
</p>
</blockquote>
<p>I assumed that would be like a portable installation, and so
searched the manual for portable, <br>
but only brought up one search result about PNGs :-) <br>
</p>
<blockquote>
<p><img src="cid:part1.Kax40KWe.Qbk8DLkc@paulanorman.info" alt=""
width="942" height="306"></p>
</blockquote>
<p>... So I'm hoping that it might be available in there somewhere?<br>
As an experimental or undocumented feature?</p>
<p>Kind regards,</p>
<p>Paul<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 1/07/2023 10:43 pm, Gilles Caulier
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHFG6sGgC046gR5OfepRUCXj_qWhJnkcHNY2gapDekRbD619JA@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">Remo,
Paul ask about windows binary tarball, with the executables only, not
the source code.
This version do not require admin right to install the program in the
home directory.
The files created under Windows by the application can be found here :
Best
Gilles Caulier
Le sam. 1 juil. 2023 à 11:31, Remco Viëtor <a class="moz-txt-link-rfc2396E" href="mailto:remco.vietor@wanadoo.fr"><remco.vietor@wanadoo.fr></a> a écrit :
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
On samedi 1 juillet 2023 10:26:45 CEST Paul Norman wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Hi,
If using a tarball like:
<a class="moz-txt-link-freetext" href="https://download.kde.org/stable/digikam/8.0.0/">https://download.kde.org/stable/digikam/8.0.0/</a>
digiKam-8.0.0-Win64.tar.xz
<a class="moz-txt-link-freetext" href="https://files.kde.org/digikam/">https://files.kde.org/digikam/</a>
digiKam-8.1.0-20230628T051544-Win64.tar.xz
And you later wanted to use the tarball for 8.1.0 when it is released
(or in the meanwhile a new pre-release from
<a class="moz-txt-link-freetext" href="https://files.kde.org/digikam/">https://files.kde.org/digikam/</a> ) — what files would you need to first
copy/backup safely, then after the new tarball (8.1.0) was unpacked over
the earlier 8.0.0 (or earlier 8.1.0 pre-release) – copy back into place
please?
TIA,
Paul
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
As far as files from the tarball are concerned, none as long as you keep the
8.0.0 archive: IMO it's better to redo the full compilation if needed, it
avoids stupid mistakes and trouble due to library changes.
I'd also unpack the 8.1.0-x tarball besides the 8.0.0 tree, in case I ever
want/need to compare the two. If you don't want to do that, and still have the
8.0.0 archive, I'd probably delete the 8.0.0 tree prior to unpacking the
8.1.0-x archive. Same when you switch to a stable version later.
As far as the installed program is concerned, it depends on how/where the
program files are installed. If you keep the 8.0.0 source tree, I'd uninstall
that version before installing a new one (avoiding subtle bugs when some
installed files change, but are not overwritten/removed). Note that that is
for the program files, NOT the user data (which should be completely separate,
and not touched by an uninstall)
</pre>
</blockquote>
</blockquote>
</body>
</html>