mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
https://www.google.com/accounts/o8/id?id=AItOawk3HGoDpnOPob5jOjvIootmkve1-nCpRiI 2013-09-25 18:28:40 +00:00 • committed by admin
parent 3368ded592
commit 811e829c54
1 changed files with 23 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
doc/forum/git-annex___38___ikiwiki_experiment/comment_4_55da5c3c41c13b08590ce1ff8117cef6._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawk3HGoDpnOPob5jOjvIootmkve1-nCpRiI"
nickname="Kalle"
subject="comment 4"
date="2013-09-25T18:28:40Z"
content="""
@Joey
> I don't know why you don't want to let git-annex sync its data to $gitdir.
Well neither do I! :) It seemed to be the way to avoid duplicating data while still having the images picked up by the ikiwiki album plugin. Wouldn't the files in the $gitdir end up duplicated in $srcdir?
> The symlinks could be occuring because of a bug in direct mode.
> (I have fixed many past bugs that caused that.) But just as likely
> it's because ikiwiki will run git pull in the srcdir.
When you mention it I've had similar problems with my vfat usb annex repos. Using the post-receive merge hook to make files visible for non git-annex devices about town. Nothing I can reliably recreate but I will keep my eye out for bugs.
> I think it would make more sense to use the underlay plugin and keep
> your annexed repository in a separate underlay.
Yep that would be ideal. For my usecase the album plugin is vital and I can't understand how album would pick up and deal with images in an underlay dir. This is a bit OT for this site though most of my questions are ikiwiki related.
"""]]