ATM git-annex init switches repository to direct mode if detects a crippled filesystem. Since version 6 is now generally more usable than direct mode in many scenarios, it would be nice if it was possible to instruct to choose v6 mode instead of direct whenever a crippled system is encountered.
Since v7, direct mode is not used by default in crippled filesystems, so done --Joey
I think that is correct. But isn't
annex initis also indirectly invoked by any annex command, e.g. if I just dogit clone URL ; cd DIR; git annex get FILEs?Yes, it will auto-init in a clone. But you can still manually init of course.
I am reluctant to add this if the only use for it is going to be until v6 becomes the default; it would make more sense to spend the time on getting v6 closer to that point.
Especially because "v6 is worth using instead of direct mode" is a pretty specific opinion to hardcode into git-annex. I can imagine other opinions, like "v6 is worth using instead of direct mode but not in WSL because sqlite sometimes crashes there" (closer to my own opinion). Seems to me that if there were a setting at all, it would need to make git-annex default to v6 mode always.
default only for the crippled FS or for all?
Anyways, it is up to you of cause. But even with your use-case (when to prefer direct instead of v6) it sounds like such an option would be handy so I could set it within ~/.gitconfig and have all new repos uniformly in
directmode (whenever v6 is the default). Especially sinceannex initseems to have no option for getting into direct mode right away, so whenever v6 becomes default there, it would require a jump first into v6 and then runningannex direct(if I am not missing anything).