On Thu, Sep 01, 2011 at 09:11:04AM -0400, Ethan wrote: > On Thu, Sep 1, 2011 at 6:05 AM, oliver <[email protected]> wrote: > > > a while ago I talked about using symbolic links. > > But I was not accurate enough in picking the terms. > > I later explained it: "symbolic links" was not meant > > as symbolic links on the filesystem level, which is > > what symbolic links are. > > > > Let me clarify. What I want *is* support for symbolic links on the > filesystem level. I'm experimenting with using git-annex to store my > picture files, so my picture library consists of symlinks to pictures. The > symlinks have appropriate names like "dscn8517.jpg", and they link to files > like > ".git/annex/objects/8x/k7/WORM-s1985206-m1306675740--dscn8517.jpg/WORM-s1985206-m1306675740--dscn8517.jpg".
Aha. I didn't know of git-annex. I used git as repository for my files, when preparing an exhibition. The disadvantage is: the files are in the working directory as well as in the repository, which means: there is at least twice as much disk spce used as I would need for the pictures... and with every new file-version mo0re space is needed. (But I have versioning, which migth become very helpful). After my work was done I removed the .git and saved disk space. I had the original phpotgraphs elswehere and the work for printing in the pic-working dir. I may also look at git-annex. Not sure if it provides what I'm looking for, but AFAIK git is written as libraries and interfaces to the user, so the functionality should be available for own programs. I tried "-d" switch from shotwell with relative pathnames. The db-dir was created relative to the $HOME. I hope it also will work with absolute pathnames, because then i could use $ shotwell -d <abspath_to_picdir> which comes close to my attempt with picture-repositories, which contains the pictures as well as the database. This would be done if I use $MY_PICTURE_DIR as path to the picture files as well as for "-d". I hope the abspath-attempt will work. Did not tried so far. If it does, then the only problem is, that there is no meta-view, which automatically shows me the picture-repositories all in shotwell overview/menus. Then I could pick out one or more of those repos, e.g. one is on USB, another is on changebale HDD under /mnt/pics/ and the rest is on my main HDD somewhere in $HOME or so. At the moment one would need to start another shotwell -d <mypiypath> program to get access to other picture-repos. > > I'd like these files to be recognized at all when I start shotwell. If the > links are broken, I'm OK with them being marked as "missing". In a perfect > world, if they got shuffled around, I would like them to not be re-imported > as duplicates. Shotwell does check files on importing. I tried at least with some jpg-files and it works. Don't know if it also can handle some 10k or some 100k files efficiently. Also I don't know how it compares files to check on equality. But it seems, for jpeg-files it checks the pure data-part. But if it finds equally data-dart files, it *might* be fine, to ask, if other comments parts from the files might be added to the database, so that pictures with differing comment sections but similar jpg-data might yield in adding all the found comment parts, so that no comment is missing. Would be nice, but is a rather minor feature (nice to have, but not extremely important). > > Shotwell currently explicitly doesn't support symbolic links as "images" > (see BatchImport.vala:1444 and DirectoryMonitor.vala:69). I can understand > that it might be complicated to figure out how to treat them; [...] Symlinks are not that complicated. But it might need some more syscalls to check that. => man 2 stat => man 2 lstat Ciao, Oliver _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
