First line of the readme:
vdm is an alternative to e.g. Git Submodules for managing arbitrary external dependencies for the same reasons, in a more sane way.
Yes. I saw that. I was giving you my assessment based on the rest of the technical details in that readme. It doesn’t look like vdm is dealing with any part of the dependency repos (.git directories) other than to download them. In fact, they even mention deleting those .git directories. Please let me know if you think I misinterpreted any of those details.
Neither does Git though. I’m not really sure I follow your point. This is clearly intended as an alternative to submodules. It says so!
I’m not saying it’s an exact copy of git submodules.
This is clearly intended as an alternative to submodules.
An alternative, not a replacement. Vdm is specifically designed to track code dependencies. There are use cases like monorepos where vdm won’t work.
Neither does Git though. I’m not really sure I follow your point.
Git does track submodule history unlike vdm.
By default, vdm sync also removes the local .git directories for each git remote, so as to not upset your local Git tree.
Git submodules don’t delete those .git directories. It uses them.
If you want to change the version/revision of a remote, just update your spec file and run vdm sync again.
This is not how git submodules or subtrees work.
vdm does depends on git being installed if you specify any git remote types
Support more than just git and file types, and make file better
Git submodules and subtrees don’t support anything other than git remotes.
