-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows: annex has issues with links in submodules so do not code testing get/install in submodule repos for now :-/ #44
Comments
actually workaround for testing would be to clone that submodule into another temp directory -- then annex works properly |
Due to the way git submodules work, if you intend to use a git-annex I do not see a way around this. (Other than using direct mode.) see shy jo |
ah right -- just stoke me that indeed if repository is initialized as an existing submodule (not added anew) its .git is just a file containing a pointer to "upstairs" .git/ directory ... lame :-/ And the only way around this was if annex was not hidden under .git/annex but rather was an independent directory in the root of the repository (e.g. as .annex). So is important to keep it in mind as a limitation of git-annex then (existing independent annex'ed repos can't be used as submodules), heh heh |
@joeyh but how much git-annex relies on hardcoded .git/annex path? ;) i.e. may be some time there could be an option to initialize it outside of the .git/? ;) |
Even though I have marked it as 'wontfix' for now: I have initiated a new milestone (Git-annex: big refactoring 1) where we could collate those issues we identified, you agree that they are worth tackling, but it would require a massive refactoring of annex code/structure. For now I have placed there #32 since you are already dealing with it somewhat, and it might be worth moving this #44 there? |
Yaroslav Halchenko wrote:
It might work to replace the "gitlink" file with a symlink. see shy jo |
replacing .git with a symlink sounds like begging for a trouble ;) but I could be proven wrong (that git folks envisioned this crippled .git file as a cross-platform symlink replacement and otherwise test proper git functioning whenever .git is a symlink to somewhere high up ;)) |
(My email reply was rejected by github for some reason. Repost.)
I tried it, and it seems to work ok, at least for the limited number of See:
It would be ok using the above approach, a submodule then uses the same |
I've added submodule support to git-annex http://git-annex.branchable.com/submodules/ Still needs testing, and it's known to not work in FAT or Windows yet, see shy jo |
cool, thank you @joeyh . tested with a fresh build of git-annex(avail from neurodebian -devel now for jessie/sid) and indeed works smoothly. I will wait for your go on windows/OSX to consider it resolved fully. Cheers! |
Yaroslav Halchenko wrote:
Submodules should work portably since cf903d5a3c42afd569ff0c1a2202c0e0168b6f8f see shy jo |
splendid. thank you @joeyh. I will close it then |
not yet fully resolved, thus will reopen for now |
Yaroslav Halchenko wrote:
I'm sorry, but as a bug report, this is completely incoherent. Happy to help if I can get a textual description of how to reproduce (Also, why reopen a bug report? Bug numbers are not a scarce resource, see shy jo |
Adjust figure 1 from @mih + elaborate captions for both figures
http://git-annex.branchable.com/bugs/downloads_load___40__from_url__41___to_incorrect_directory_in_a_submodule/
The text was updated successfully, but these errors were encountered: