https://bugs.kde.org/show_bug.cgi?id=377587
Bug ID: 377587 Summary: The --database-directory argument should also be the location of the digikamrc file when used Product: digikam Version: 5.4.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Database-Setup Assignee: digikam-de...@kde.org Reporter: developm...@efficientek.com Target Milestone: --- The intent of the --database-directory command line option is to allow for multiple independent DK databases and instances. However the current usage of the application wide config file, digikamrc, is at odds with this. The digikamrc file can not be specified on the command line, so there is only one per user, even though there may be multiple digikam databases. Since the digikamrc file has some settings that definitely should be different per digikam database instance, such as the "Database Settings", there should be a way to specify a different digikamrc file when selecting a non-default database instance. I suggest that the directory specified via --database-directory be the directory where the digikamrc file is expected. This would be a very simple to fix by modifying the KSharedConfig construction at https://cgit.kde.org/digikam.git/tree/app/main/main.cpp#n150. If commandLineDBPath is null do what is done now, otherwise do construct like: KSharedConfig::openConfig(commandLineDBPath + QLatin1String('/digikamrc')) This will make digikam instances truely independent and should have the added benefit of fixing bug 218297 as well. -- You are receiving this mail because: You are watching all bug changes.