[Shotwell] Call for testing

[Adam Dingle]

On 12/11/2010 06:14 AM, Andrea Carpani wrote:
> On 12/11/2010 04:35 AM, Jim Nelson wrote:
>> We've been working diligently on Shotwell 0.8 and are looking to begin
>> wrapping up this release.  Several exciting features have been added as well
>> smaller additions and bug fixes.  This release includes such features as:
>>
>> * Video support, including uploading videos to various Web services
>> (including YouTube)
>> * Runtime monitoring and auto-import of the library directory
>> * Metadata (tags, titles, rating) written to master files automatically
>> * Flagging files for batch operations
>> * Set multiple photos to desktop background slideshow
>> * ... and more!
> I've built trunk successfully (Ubuntu Maverick, no additional libraries)
> and I'll be happy to test it, but on my laptop I'm already using the
> "Maverick" version of shotwell: is there a way I can test the trunk side
> by side the stable shotwell?
>
> I've installed the trunk on a separate directory and I know I can change
> the datadir with -d option, but what about cgonf preferences? Is there a
> way I can start the trunk without polluting the "stable" conf?

Not at this time.  You can run two versions of Shotwell side by side and 
they will share the same GConf keys, and this should be mostly OK.  Both 
versions, however, will have the same library directory (specified via 
"Import photos to:" in the preferences dialog).  This means that any 
photos you import from a camera into one version will be visible in the 
other.  You should also be aware that the trunk version of Shotwell will 
write metadata to photo files if you tell it to, so if you're sharing 
photos between Shotwell 0.7.2 and Shotwell trunk then the trunk build 
may be writing to files in your 0.7.2 library.  We think this is 
reasonably safe today, but it's still a trunk build - caveat emptor.  :)

In the future, we may store a separate import directory for each profile 
(i.e. data directory), or even an entirely separate set of GConf keys 
for each profile; see http://trac.yorba.org/ticket/2146 .  This would 
reduce the potential interaction between two versions running side by 
side if you use a separate profile for each version.

adam