[Shotwell] Copying shotwell data to another platform
Peter DO Smith
pdo.smith at gmail.com
Thu Jul 29 00:13:38 PDT 2010
On Wed, Jul 28, 2010 at 4:12 PM, Adam Dingle <adam at yorba.org> wrote:
> Peter,
>
> On Mon, Jul 26, 2010 at 8:50 PM, Peter DO Smith <pdo.smith at gmail.com>wrote:
>
>>
>> This raises the more general question of copying a Shotwell library to
>> another machine in a different location. Do you plan to make provision for
>> that?
>>
>
> Perhaps we could add a command to save the entire library plus Shotwell's
> database to an archive which could be copied to another machine. Feel free
> to file a ticket if you'd like to see that.
>
> Over time, I hope we can keep more of Shotwell's state (including, for
> example, thumbnails) in the directories where photos live. If we could ever
> get to the point where *all* of Shotwell's state is stored in those
> directories then you'd be able to copy to another machine simply by copying
> the library directory itself, which would be nice. I don't think that will
> happen in the foreseeable future, though.
>
>
> Thanks for your reply Adam.
I keep my .shotwell folder in my photos folder by the simple expedient of
passings its path via the -d command line switch (great feature by the way).
This allows me to easily backup the photo library and the Shotwell state all
in one go. Currently I backup my home photo library to a USB drive (using
Unison) and then restore it to my office machine. I have taken care to
ensure that my office machine and home machine use identical paths so that
the sqlite database need not be changed.
I am going to write a simple command line utility in Python to adjust the
paths in the sqlite database and give me more flexibility.
Peter
More information about the Shotwell
mailing list