On 23/11/16 05:28 am, Jonas Diemer wrote:
Hi James,
thanks for your quick reply. The problem is that darktable creates
XMP files for each and every imported photo. These files appear in
typical file browsers (alphabetically in between the image files),
which makes it harder to browse photos with these. In my case, I use
a central photo repository on a NAS and not all users use darktable -
and everyone who isn’t complains about the XMP files.
I understand why the files are created and find them a good idea. I
just would like to have the option of hiding the files from others.
Currently, I have to manually run chflags to hide them - it would be
great to have darktable do that automatically.
My workflow is to have my raw files symlinked into a directory
hierarchy by year and month, and import from that directory to
darktable. The xmp files stay there, and it's out of the way.
Anybody who wants to look at the image files can look at the
original dir, and I export to jpeg format in an entirely different
part of the tree after processing.
eg
original dir symlinked to
$TOP/EOS_100D/100CANON $TOP/darktable/2016/2016-01
export dir
$TOP/photos/2016/2016-01
Perhaps something like that would work for you?
James C. McPherson
--
Solaris kernel software engineer, system admin and troubleshooter
https://www.jmcpdotcom.com/blog
Find me on LinkedIn @ http://www.linkedin.com/in/jamescmcpherson
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to [email protected]
