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

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2019-06-27 19:08:46 -04:00
commit c05c73657c
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 38 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/todo/external_backends/comment_3_9451d002f6768dd5975d5816c12b1350._comment Normal file
View file

@ -0,0 +1,15 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="comment 3"
date="2019-06-26T20:15:19Z"
content="""
Thanks a lot @joeyh for looking again at supporting external backends.
I think the issues with missing backend implementations are similar to issues with a missing external special remote implementation: something that the repo owner/maintainer needs to deal with. I periodically forget to put mine into the PATH, and then `git-annex` tells me to a special remote available. Fixing these issues has been manageable in practice.
For reference, these are some of the todos that support for external backends would obviate: [[todo/key_checksum_from_chunk_checksums]] [[todo/MD5E_keys_without_file_size]] [[todo/preserve_file_extensions_in_WORM_and_URL_keys]] [[todo/option_to_add_user-specified_string_to_key]] [[todo/add_xxHash_backend]] .
"""]]

13
doc/todo/external_backends/comment_4_2983bbf5e1cc485da3e8e9628a4bea89._comment Normal file
View file

@ -0,0 +1,13 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="some todos that external backends would obviate (fix formatting, add one)"
date="2019-06-26T20:25:50Z"
content="""
* [[todo/key_checksum_from_chunk_checksums]]
* [[todo/MD5E_keys_without_file_size]]
* [[todo/preserve_file_extensions_in_WORM_and_URL_keys]]
* [[todo/option_to_add_user-specified_string_to_key]]
* [[todo/shorter_keys_through_better_encoding]]
"""]]

10
doc/todo/external_backends/comment_5_37fd824cf9f2dcc59616b9d49e38c262._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="Ilya_Shlyakhter"
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
subject="comment 5"
date="2019-06-26T20:38:19Z"
content="""
P.S. It seems that in case of missing backend implementation, the handling should revert to exactly what currently happens for WORM/URL keys? Except with a different warning message, as custom backends are _potentially_ verifiable.
If git-annex could support [[todo/alternate_keys_for_same_content]], then for a download from an external backend key you could also compute a standard checksum-based key (e.g. MD5 or SHA256), and record its presence in the remote you got the contents from, and the correspondence to the external backend key. Then, at least, if this contents gets uploaded somewhere else, it would be verifiable even without the external backend implementation.
"""]]