[Digikam-devel] problems with digikam3.db into a nefs partition

Fabien fabien.ubuntu at gmail.com
Wed Mar 7 09:49:33 GMT 2007


Hello,

Achim Bohnet wrote:
> On Monday, 5. March 2007, Fabien wrote:
> 
>>Hi,
>>
>>Please, please, evaluate my proposal :
>>http://bugs.kde.org/show_bug.cgi?id=107871#c6
>>
>><<
>>I suggest to add 2 command-line options to start digikam.
>>
>>* -f to to specify the full path to digikam3.db, or relative path from 
>>the album directory
>>
>>* directory as argument => this would be the album path digikam use
>>
>>Eg:
>>
>>1) # digikam
>>would behave like now. The 1st time, it will ask for an album path
>>
>>2) # digikam -f /path/to/digikam3.db
>>would behave like now except it will use the specific path for the 
>>database file
>>
>>3) # digikam /path/to/my/album
>>digikam will use this directory as the album path, but won't override 
>>default album path if there's already one
>>
>>4) # digikam -f /path/to/digikam3.db /path/to/my/album
>>would combine 2) and 3)
>> >>
>>
>>This would not only be a workaround for the nfs/samba locking problem, 
>>but also a way to extend digiKam's usage :
>>some people complain that they can only use one library which stores all 
>>their pictures. They'd like to have a few libraries. There are also some 
>>  people who'd like to access pictures on a read-only media (eg DVD). 
>>Finally, some people would also like to open a specific directory which 
>>contains pictures, like you can do with other tools.
>>All these wishes could be mostly solved by this addon...
> 
> 
> I agree with your points 1-4.   Nevertheless from user point of
> view having a warning when pictures are on a remote file system, like:
> 
> 	Your picture library is on a remote file system.
> 	The digikam's database can't be stored there. 
> 	Please spezify a local folder
> 
> 		[Browse ...]    [Quit]
> 
> Is much more helpful.

Well, yes it could be useful, but doesn't solve the problem :)
Note: "can't" is not the best word. It can work perfectly fine, even on 
a remove fs.

> Feel free to cut and paste to your bug report of post the bug# ;)

There's a warning in the configuration page. But, I guess the same 
warning could be added the first time digiKam is started, when it asks 
for an album library path.

And, about my proposal, don't forget it's not only about this locking 
problem, it's also about adding requested features...
I'm sure digiKam loses a lot of users because of the different use cases 
I mentionned above that digiKam doesn't address right now.
IMHO, it's really a pity...

--
Fabien




More information about the Digikam-devel mailing list