diff options
| author |  http://joeyh.name/ <http://joeyh.name/@web> | 2012-09-09 17:22:58 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2012-09-09 17:22:58 +0000 |
| commit | b58557b71eb10f48ec1b9b8f72e5c1fe225afd22 (patch) | |
| tree | fa644cdd6415997be9c4869a06cdeeb68f2824b8 /doc | |
| parent | d49a71f9707978963514ad69e62a0a6ca199add7 (diff) | |
Added a comment
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/forum/Weird_behavior_with_OS_X_Finder_and_Preview.app/comment_1_8c8d86790a9d31518f9bb96a2d2dafee._comment | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/forum/Weird_behavior_with_OS_X_Finder_and_Preview.app/comment_1_8c8d86790a9d31518f9bb96a2d2dafee._comment b/doc/forum/Weird_behavior_with_OS_X_Finder_and_Preview.app/comment_1_8c8d86790a9d31518f9bb96a2d2dafee._comment new file mode 100644 index 000000000..4234eac2b --- /dev/null +++ b/doc/forum/Weird_behavior_with_OS_X_Finder_and_Preview.app/comment_1_8c8d86790a9d31518f9bb96a2d2dafee._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.153.8.30" + subject="comment 1" + date="2012-09-09T17:22:58Z" + content=""" +It is unfortunate that certain badly-coded programs fall over on symlinks. In theory, any program that doesn't try to be too smart for its own good will see a symlink as just like the file it links to, and should behave the same. This is the theory that led me to use symlinks in git-annex. But some programs say \"oh, a symlink! Let's see what file that's pointing at, and behave differently!\" I don't understand the mindset that leads to this kind of program being written, unless it's a program like `cp`, that has very good reasons for (at your command) following symlinks or not. + +I know absolutely nothing about Mac OSX, having never used it (except for in a ssh session while porting git-annex to it). But I have seen a similar problem with the FBReader ebook viewer. [Bug report](http://bugs.debian.org/685433) + +I was able to work around that bug by migrating my files to the SHA256E backend. This ensures that the keys stored in git-annex have extensions like .pdf etc, similar to the symlinks that point to them. You might try migrating some of your files too, and see if it makes OSX behave better. Although I thought OSX didn't rely on file extensions to determine file type.. + +Anyway, the command is: + + git annex migrate --backend=SHA256E + +I have been considering switching the default backend to SHA256E to avoid this type of problem. Your testing will be important grist for that decision. +"""]] |