On 19/10/12 11:13, Jens Fendler wrote:
>> If so, why not just do a "mv a b"? In Linux at least, the inode
>> will still be the same so the current instance of dt will operate
>> correctly. Then, on restart, dt will find the new/old db.
> Moving away an open file under a running program's butt is almost
> always a bad idea (unless you know exactly what you're doing). Further
> I/O only works as desired if the file is moved on the same device (but
> this property should be transparent to the user..), otherwise mv
> simply uses cp under the hood.
>
> If changing the library name from within DT should be possible, then I
> guess the only sane option is to
> a) remember the new library name, and
> b) immediately inform the user that a restart is required in order for
> changes to be in effect, with an option of restarting dt immediately.
>
I'm a fan of KISS, especially for corner cases like this. My proposals:
a) Add something about 'cd .config/darktable && cp library.db
backuplib.db' to a FAQ
or
b) Add administrative command line parameters to darktable (which may be
reused for other misc stuff like extracting lists of images and similar
fun to do batch stuff if anyone sees a good use case for that), e.g.:
darktable --adm --copy_lib newlibname.db
darktable --adm --move_lib newlibname.db
I think I vote (a).
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel
