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

Added a comment: imports and symlinks

Browse source
This commit is contained in:
Ilya_Shlyakhter 2022-08-22 20:40:42 +00:00 committed by admin
parent cbc26acd45
commit 274ef9db2a
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/bugs/git-annex-import_imports_outside_of_directory/comment_10_30dab036949bd35e026a31974c4e5164._comment Normal file
View file

@ -0,0 +1,16 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="imports and symlinks"
date="2022-08-22T20:40:41Z"
content="""
> the old git-annex import already skipped symlinks to files
Then the old import was problematic as well :)
Sorry for harping on this, but since this affects my use cases (and I suspect others' as well), what's the rationale for not doing what `tar` does?
I assumed that an import is similar to doing a `tar` or a `cp -pr`, except that the files get annexed and a connection to the files' origin is recorded.
For things like song collections the symlinks might not matter, but for datasets they do. E.g. symlinks are used to ensure tools that expect certain filenames at certain paths can find them. The tools are often written by other people, so as a user you might not know all details of these expectations. Files from related analyses are symlinked to keep the relation explicit.
Absolute symlinks are used to point to large shared resources (e.g. genome files) on a filesystem that all users of the repo share. I can give more detailed illustrations if it would help. But I'm not sure I understand the downside of importing symlinks the way tar does.
"""]]