In git-annex-setpresentkey, could an option be added to record in aaa/bbb/*.log.cnk that the key contents is present in chunked state, with a given number of chunks of a given size?
In git-annex-setpresentkey, could an option be added to record in aaa/bbb/*.log.cnk that the key contents is present in chunked state, with a given number of chunks of a given size?
I would rather not complicate setpresentkey with things not related to presence information.
This seems pretty deep into messing with git-annex's internals to seem plausible to me as a separate command. At some point, you may as well just write data to the branch yourself. What is the use case?
"What is the use case?" -- to register with git-annex the presence of a file in a remote, that is already split into chunks, without downloading the file. "I would rather not complicate setpresentkey with things not related to presence information" -- makes sense. "you may as well just write data to the branch yourself" -- yes; just wasn't sure if that might break some invariant, e.g. between the branch and the SQL databases derived from it.
Don't worry about this todo, I'll figure it out.
That's the use case I'd guessed, but it seems things would have to line up exactly for it to work. Ie, I think git-annex requires all the chunks to be the same size, and may fail in unexpected ways if they are not.
You do not need to worry about any internal caching when modifying the git-annex branch, because updates to the git-annex branch are always being merged from remotes, so any such caching has to detect changes and update itself.