[digiKam-users] repointing new 7.5 upgrade to old 6.0 collection with existing files

[Gilles Caulier]

Hi,

yes there are more config files for digiKam, but the most important is the
INI based config file digikamrc:

[F] C:/Users/_account_/AppData//Local/digikamrc
[F] C:/Users/_account_/AppData//Local/digikamsystemrc
[F] C:/Users/_account_/AppData//Local/digikamtagsmanagerrc
[F] C:/Users/_account_/AppData//Local/showfotorc

[D] C:/Users/_account_/AppData//Local/digikam/
[D] C:/Users/_account_/AppData/Roaming/digikam/
[D] C:/Users/_account_/AppData/Roaming/showfoto/

Gilles Caulier


Le mer. 26 janv. 2022 à 16:52, Ty Mayn <tyrus.mayn at gmail.com> a écrit :

>  I see that another way of hiding a working program and collection during
> the transition to a new version is to create a new user and segregate until
> the new version is proven.
>     It seems to me that hiding the digikamrc file alone is sufficient to
> let the new program show its true colors.
> But let me return to the events of a new install
> 1. will the install process seek to use the same "digiKam" folder in
> Program Files
>      if so I will ask the install to go somewhere else
> 2. digikamrc    Is there any other file which is serving as the persistent
> memory of chosen display and behavior variables for digikam?
>          Does the installation code ask for install to probe for
> digikamrc  and inherit/preserve any settings that have been chosen within
> older version operations?
>          Does installation look in /User/user/AppData/Local for at least
> on occurrence of a digikamrc (evidence of a preexisting install)?
>          Are there any other files for persistence of program
> config,behavior, or carryover data?
>       Would it not be sufficient to just hide digikamrc away from
> /user/AppData/Local  during a new install
>      and then edit the newly arrived digikamrc for the database path
> statements?
>    I am OK with having a clean slate of default  config variables in the
> newly delivered digikamrc
>
> 3. database files    I hope that digikam installation does not go probing
> through a hard drive looking for possible collections or recognizable names
> of database files.     I much prefer to point a program to its place of
> work.
>     So perhaps I dont have to "hide" the database files  or temporarily
> move them off of the drive as I intended in the plan at the top of this
> thread.  So if the install program is not aggressive about automatically
> searching for existing database in all readable folders  then I can
> temporarily hide the database files  simply by not offering a digikamrc file
>
>        Hiding the entire user is one way to hide the digikamrc file ....is
> that the only critical file to hide  to get a new config?
> Thanks
> Ty
>
>
> On Wed, Jan 26, 2022 at 12:33 AM Gilles Caulier <caulier.gilles at gmail.com>
> wrote:
>
>> Hi,
>>
>> To be sure to not break something in config files, I recommend to create
>> a new user account, and to start digiKam 7.5.0 from this account as well
>> without touching all settings from the original account. Like this there is
>> no risk of losing/breaking something.
>>
>> Best
>>
>> Gilles Caulier
>>
>> Le mer. 26 janv. 2022 à 06:24, Ty Mayn <tyrus.mayn at gmail.com> a écrit :
>>
>>> Now returned to digikam, It's time to upgrade from 6.0 to7.5
>>> Unfortunately I have to use windows10 for the benefit of a non linux
>>> collaborator.
>>> i have looked but not found a howto on upgrade. Can I describe my
>>> strategy and receive warning away from any wrong assumptions.
>>>       I plan to install new 7.5 with all evidence of the old 6.0 hidden.
>>> I will hide the existing config file digikamrc and the 4 database files.
>>>  After the install, I guess I will find a new default digikamrc in the
>>> path
>>> User/AppData/Local (if that default has not changed)
>>>     I expect to be greeted by a welcome wizard that will ask to point to
>>> some brand new folders to become albumsbut rather than follow the wizard:
>>>    I hope to return the database files into their original location
>>> specified in the older digikam RC
>>>     I plan to examine the new config file and pause to compare some of
>>> its config variables compared to the older.
>>>    Then  manually edit the path variables in digikamrc which point to
>>> the  database files.
>>>        I am not trying to circumvent any tools that might be in the
>>> wizard and  may be its not oriented to starting up an all new album
>>> collection from scratch.
>>>       I am guessing the database files can serve the new version and may
>>> change or be repaired with  ongoing use  (unless warned away)
>>>     This seems to be a worthwhile approach for pointing a new program
>>> install to an existing collection..... unless this helpful list warns me in
>>> other directions.
>>> Thanks
>>> Ty
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20220127/f3c6824c/attachment-0001.htm>